Enhancing file indexing of block-level backup copies of virtual machines and/or file systems by populating and tracking a cache storage area and a backup index

ABSTRACT

An illustrative approach accelerates file indexing operations for block-level backup copies in a data storage management system. A cache storage area is maintained for locally storing and serving key data blocks, thus relying less on retrieving data on demand from the backup copy. File indexing operations are used for populating the cache storage area for speedier retrieval during subsequent live browsing of the same backup copy, and vice versa. The key data blocks cached while file indexing and/or live browsing an earlier backup copy help to pre-fetch corresponding data blocks of later backup copies, thus producing a beneficial learning cycle. The approach is especially beneficial for cloud and tape backup media, and is available for a variety of data sources and backup copies, including block-level backup copies of virtual machines (VMs) and block-level backup copies of file systems, including UNIX-based and Windows-based operating systems and corresponding file systems.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/893,000 filed on Aug. 28, 2019, which is incorporated byreference herein. Any and all applications for which a foreign ordomestic priority claim is identified in the Application Data Sheet ofthe present application are hereby incorporated by reference in theirentireties under 37 CFR 1.57.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentand/or the patent disclosure as it appears in the United States Patentand Trademark Office patent file and/or records, but otherwise reservesall copyrights whatsoever.

BACKGROUND

Businesses recognize the commercial value of their data and seekreliable, cost-effective ways to protect the information stored on theircomputer networks while minimizing impact on productivity. A companymight back up critical computing systems such as databases, fileservers, web servers, virtual machines (VMs), and so on as part of amaintenance program. Given the rapidly expanding volume of data undermanagement, companies also continue to seek innovative techniques formanaging data growth. Enterprises also increasingly view their data as avaluable asset to leverage pro-actively.

One way of leveraging backed up data is to index it for future access.Another way to leverage the backed up data is to give users the abilityto discover files and folders in backup copies, a feature known as “livebrowse.” Live browse and file indexing operations, as well as file-levelrestores, can suffer significant slow-downs when a targeted backup copyis stored in certain cloud storage environments configured in cloudservice accounts and/or on non-random-access media such as tape. In somescenarios using tape as the backup medium, live browsing and/or fileindexing is too slow to be offered as a feature. Therefore, observedperformance degradation demonstrated by cloud storage and tape storagemedia give rise to a pronounced need for improving the speed of livebrowse and file indexing operations.

SUMMARY

The present inventors devised an approach that speeds up file indexingand/or live browse operations for backed up block-level copies in anillustrative data storage management system. The approach enables livebrowse and file indexing operations to start sooner and progress faster,and thus represents a technological improvement over prior art livebrowse and file indexing features. the disclosed enhancements make livebrowse and file indexing feasible now for backup copies stored on tape.File indexing operations are used for populating the cache storage areafor speedier retrieval during subsequent live browsing of the samebackup copy, and vice versa. The key data blocks cached while fileindexing and/or live browsing an earlier backup copy help to pre-fetchcorresponding data blocks of later backup copies, thus producing abeneficial learning cycle. The approach is especially beneficial forcloud and tape backup media. File-level restore operations likewisebenefit from the illustrative approach, starting sooner and progressingfaster as well.

A cache storage area (the “live browse cache”) is used for locallystoring and serving key data blocks. In a live browse and/or fileindexing and/or file-level restore operation, data blocks arepreferentially served from the live browse cache rather than beingretrieved from the targeted backup copy, since the former operation isspeedier than the latter, especially if the backup copy resides in cloudstorage (e.g., in a cloud service account) or on tape. The cache storagearea is maintained for locally storing and serving key data blocks, thusrelying less on retrieving data on demand from the backup copy. Fileindexing operations are used for populating the cache storage area forspeedier retrieval during subsequent live browsing of the same backupcopy, and vice versa, live browse operations are also used forpopulating the cache storage area for speedier retrieval during fileindexing. Flagging the key data blocks while file indexing and/or livebrowsing an earlier backup copy helps to pre-fetch corresponding datablocks of later backup copies, thus producing a beneficial learningcycle that speeds up the subsequent operations. The approach isespecially beneficial for cloud and tape backup media, and is availablefor a variety of data sources and backup copies, including block-levelbackup copies of virtual machines (VMs) and block-level backup copies offile systems, including UNIX-based and Windows-based operating systemsand corresponding file systems. File-level restore operations likewisebenefit from the illustrative approach.

The Live Browse feature provides the ability to discover in real-timefiles and folders in a backup copy that is mounted to a component of thedata storage management system. User-driven live browse enables a userto traverse folders throughout the backup copy and see what files lietherein. File Indexing, which relies on using live browse toautomatically traverse all files and folders in the backup copy,collects information into an index that can be searched by filename andother attributes. File-indexed information (metadata) includes sourcevirtual machine identifier, source file system type, disk and volumeidentifiers, file and folder names, file types, file size, fileversions, access control list attributes, etc., without limitation.

The illustrative approach includes special handling for certain datablocks that are needed for activating live browse of a backup copy. Suchdata blocks are sometimes referred to as metadata, though not allmetadata (attributes) present in a backup copy are needed to activatelive browse. To ease the reader's understanding of the presentdisclosure, data blocks that receive special handling according to theillustrative embodiments are referred to herein as “cacheable” or“live-browse cacheable” data blocks, to distinguish them from other datablocks that are not specially handled in regard to live browse cachemanagement. Cacheable data blocks include data blocks that describe thefile system on a block device in a data source, and hence in its backupcopy, such as superblocks in Unix-based file systems, Master File Table(MFT) blocks in New Technology File System (NTFS) and otherWindows-based file systems, etc. Different file systems have differentnomenclatures, configurations, locations, sizes, and formats for theirfile-system descriptor data blocks.

The illustrative approach includes techniques for populating and usingthe special-purpose live browse cache, which is configured within a datastorage management component that is involved in creating block-levelbackup copies. An exemplary such component is a media agent that acts asa portal for generating backup copies and storing and retrieving themto/from storage. Thus, the same component that participates in creationand storage of a backup copy (the media agent) is also used for livebrowsing and/or file indexing of the backup copy. The media agentmanages live browse cache contents and serves data blocks as needed fromthe live browse cache, and if not found therein, the media agentretrieves data blocks from the targeted backup copy in backup media.

During live browse and file indexing operations, the live browse cacheis populated with certain key data blocks—the so-called “cacheable datablocks,” which are later served from the live browse cache in subsequentoperations. Data blocks read during a user-driven live browse of abackup copy are added to the live browse cache, unless already presenttherein. Likewise, data blocks read in a file indexing operation arealso added to the live browse cache, unless already present therein.Live browse/file indexing and file-level restore performance isoptimized when the live browse cache was previously populated with alldata blocks needed for the present operation.

During backup operations, a data agent, which is another component ofthe data storage management, plays a key role. In some configurations,the data agent associated with the source virtual machine and/or filesystem recognizes cacheable data blocks (e.g., file-system descriptorblocks) when backing up source data. The data agent flags such datablocks as cacheable data blocks to be added to the live browse cache. Insuch a scenario, the live browse cache is populated at least in partwhen the initial backup copy is created, because the data agent has theintelligence to identify cacheable data blocks. These blocks then becomeavailable from the live browse cache on the next live browse/fileindexing operation that mounts the particular backup copy. In thisscenario, performance benefits of using the live browse cache arerealized on the next operation that follows the initial backup.

However, in some configurations, the data agent involved in the backupoperation does not recognize some or all of the cacheable data blocks inthe data source, and therefore cannot populate the live browse cachewhen creating the backup copy. In such scenarios, the subsequent livebrowse/file indexing operation experiences slower performance as some orall of the needed data blocks are recalled on demand from the backupcopy in backup media. These recalled data blocks are captured and addedto the live browse cache for future use. This feature is especiallyuseful for live browsing block-level backup copies from certain filesystems where the file-system descriptor blocks are not known orrecognized by the originating data agent, e.g., EXT4 without limitation.Such scenarios in the prior art would always experience slow live browseand file indexing, or might even time out altogether, because datablocks would always be recalled from backup media. However, theillustrative approach cures this deficiency by using post-backup livebrowse and file indexing operations to collect cacheable data blocks andpopulate the live browse cache for future use, thus enabling second andlater live browse operations to be faster than the first. In someembodiments, the data agent performing a backup operation queries forlive browse cache contents as a guide to flagging source data blocks ascacheable in the present backup.

User-driven live browse viewing patterns are not generally predicted bythe data agent and/or media agent involved in creating a backup copy.Instead, the illustrative approach captures read data blocks accordingto viewing patterns of each individual backup copy, so that the livebrowse cache can be tapped as needed in future live browse/file indexingoperations. Thus, every live browse is an opportunity to add to the livebrowse cache and improve a subsequent round of live browse/file indexingand/or improve the precision of flagging data blocks in a subsequentbackup operation. A frequency “heat map” tracks whether certain datablocks see repeated live browse access. The heat map is used for pruningthe live browse cache when cache storage space reaches certain limits.

As noted, file indexing relies on an underlying live browse operationthat automatically navigates all of a backup copy. Instead ofuser-driven on-demand live browsing, which may selectively browse onlysome portions of a backup copy, file indexing scans the entire directorytree through the live browse mount point. File indexing scans the entiretree of each backup copy, whether a full backup copy, an incrementalbackup copy, a differential backup copy, etc. Thus, file indexinginvokes live browse and methodically traverses all drive letters,directories/folders, and files in the backup copy. Read requests areissued as directories and file names are traversed, and data blocks arepreferentially served from the live browse cache; if not found therein,they are recalled from the backup copy in backup media. Data blocksrecalled from backup media are added to the live browse cache and willbe used again, thereby speeding up the performance of subsequentuser-driven live browses of the same backup copy. In a file indexingoperation, the media agent indexes the filenames and correspondingdirectories into a data structure (the “file index”) associated with theblock-level backup copy. The file index is stored at the media agent andis also persistently added to backup media.

The illustrative approach enhances backup operations to facilitate theuse of the live browse cache. When a backup copy is created, the mediaagent tracks where each data block is stored within the backup copy onbackup media and stores the tracking information in a data structureillustratively referred to as the “backup block index.” The backup blockindex is associated with the backup copy and is stored to persistentbackup media. The media agent retains the backup block index for futureuse when recalling data blocks from backup media. According to someillustrative embodiments, the backup block index additionally trackswhether each data block is live-browse cacheable, e.g., by adding acacheable flag. Cacheable flags are added to the backup block index atbackup time when the block-level backup copy and the backup block indexare created. Whether a data block is classified as cacheable isdetermined by the data agent involved in creating the backup copy, basedon one or more of: recognizing cacheable data blocks in the source data,information obtained from flags in a preceding version of the backupblock index, and/or from contents of the live browse cache. Thus, pasthistory in regard to whether data blocks are cacheable is exploited incertain future backup operations as an ongoing learning process. In someembodiments, cacheable flags in the backup block index of a precedingbackup copy are used in subsequent file indexing operations to pre-fetchsequentially data blocks from the backup copy in backup media.Sequential pre-fetching improves the performance of the ongoing fileindexing operation as compared to serving random reads issued by theoperating system. Thus, even in cases where the live browse cache isempty, unusable, or otherwise unavailable, previously identifiedcacheable flags can be exploited to improve the performance of a livebrowse/file indexing operation. Because the backup block index is storedto persistent backup media (unlike the live browse cache), cacheableflags are available in case the live browse cache is wiped or otherwiselost, e.g., if the media agent fails.

Using and managing the live browse cache, and additionally flaggingcacheable data blocks, enables live browse and file indexing operationsand file-level restore operations to start sooner and progress faster.Moreover, it is now feasible to use the illustrative approach to livebrowse and file index block-level backup copies stored on tape. Theillustrative embodiments are designed to work with any kind of sourcevirtual machine and/or file system, so that at least the second round oflive browse/file indexing operations will be faster than the first roundby taking advantage of faster data recalls from the live browse cache.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram illustrating an exemplary informationmanagement system.

FIG. 1B is a detailed view of a primary storage device, a secondarystorage device, and some examples of primary data and secondary copydata.

FIG. 1C is a block diagram of an exemplary information management systemincluding a storage manager, one or more data agents, and one or moremedia agents.

FIG. 1D is a block diagram illustrating a scalable informationmanagement system.

FIG. 1E illustrates certain secondary copy operations according to anexemplary storage policy.

FIGS. 1F-1H are block diagrams illustrating suitable data structuresthat may be employed by the information management system.

FIG. 2A illustrates a system and technique for synchronizing primarydata to a destination such as a failover site using secondary copy data.

FIG. 2B illustrates an information management system architectureincorporating use of a network file system (NFS) protocol forcommunicating between the primary and secondary storage subsystems.

FIG. 2C is a block diagram of an example of a highly scalable manageddata pool architecture.

FIG. 3A is a block diagram illustrating some salient portions of asystem 300 for improving performance of live browsing, file indexing,and/or file-level restoring of a block-level backup copy of virtualmachine data, according to an illustrative embodiment.

FIG. 3B is a block diagram illustrating some salient portions of asystem 300 for improving performance of live browsing, file indexing,and/or file-level restoring of a block-level backup copy of file systemdata, according to an illustrative embodiment.

FIG. 4 is a block diagram illustrating some details of data backup andretrieval components 315 in system 300.

FIG. 5 is a block diagram illustrating certain operations and data flowsin a block-level backup in system 300, wherein the type of sourcevirtual machine/file system is known to the originating data agent.

FIG. 6 is a block diagram illustrating certain operations and data flowsin a user-driven live browse operation that follows the block-levelbackup of FIGS. 5 and/or 8A/8B.

FIG. 7 is a block diagram illustrating certain operations and data flowsin a file indexing operation that follows the block-level backup ofFIGS. 5 and/or 8A/8B.

FIG. 8A is a block diagram illustrating certain operations and dataflows in a block-level backup (Full Backup) in system 300, wherein thetype of source virtual machine/file system is unknown to the originatingdata agent.

FIG. 8B is a block diagram illustrating certain operations and dataflows in a block-level backup (Incremental or Differential Backup) insystem 300, wherein the type of source virtual machine/file system isunknown to the originating data agent.

FIG. 9 depicts some salient operations of a method 900 according to anillustrative embodiment based on FIGS. 5-7 .

FIG. 10A depicts some salient operations of a method 1000 according toan illustrative embodiment based on FIGS. 8A, 8B, 6, and 7 .

FIG. 10B depicts some additional salient operations of method 1000.

DETAILED DESCRIPTION

Detailed descriptions and examples of systems and methods according toone or more illustrative embodiments of the present invention may befound in the section entitled LIVE BROWSE CACHE MANAGEMENT FOR FASTERLIVE BROWSING AND FILE INDEXING OF BACKUP COPIES, INCLUDING BLOCK-LEVELBACKUP COPIES OF VIRTUAL MACHINES AND/OR FILE SYSTEMS as well as in thesection entitled Example Embodiments, and also in FIGS. 3A-10B herein.Furthermore, components and functionality for improving live-browseperformance may be configured and/or incorporated into informationmanagement systems such as those described herein in FIGS. 1A-1H and2A-2C.

Various embodiments described herein are intimately tied to, enabled by,and would not exist except for, computer technology. For example, livebrowse cache management as described herein in reference to variousembodiments cannot reasonably be performed by humans alone, without thecomputer technology upon which they are implemented.

Information Management System Overview

With the increasing importance of protecting and leveraging data,organizations simply cannot risk losing critical data. Moreover, runawaydata growth and other modern realities make protecting and managing dataincreasingly difficult. There is therefore a need for efficient,powerful, and user-friendly solutions for protecting and managing dataand for smart and efficient management of data storage. Depending on thesize of the organization, there may be many data production sourceswhich are under the purview of tens, hundreds, or even thousands ofindividuals. In the past, individuals were sometimes responsible formanaging and protecting their own data, and a patchwork of hardware andsoftware point solutions may have been used in any given organization.These solutions were often provided by different vendors and had limitedor no interoperability. Certain embodiments described herein addressthese and other shortcomings of prior approaches by implementingscalable, unified, organization-wide information management, includingdata storage management.

FIG. 1A shows one such information management system 100 (or “system100”), which generally includes combinations of hardware and softwareconfigured to protect and manage data and metadata that are generatedand used by computing devices in system 100. System 100 may be referredto in some embodiments as a “storage management system” or a “datastorage management system.” System 100 performs information managementoperations, some of which may be referred to as “storage operations” or“data storage operations,” to protect and manage the data residing inand/or managed by system 100. The organization that employs system 100may be a corporation or other business entity, non-profit organization,educational institution, household, governmental agency, or the like.

Generally, the systems and associated components described herein may becompatible with and/or provide some or all of the functionality of thesystems and corresponding components described in one or more of thefollowing U.S. patents/publications and patent applications assigned toCommvault Systems, Inc., each of which is hereby incorporated byreference in its entirety herein:

-   -   U.S. Pat. No. 7,035,880, entitled “Modular Backup and Retrieval        System Used in Conjunction With a Storage Area Network”;    -   U.S. Pat. No. 7,107,298, entitled “System And Method For        Archiving Objects In An Information Store”;    -   U.S. Pat. No. 7,246,207, entitled “System and Method for        Dynamically Performing Storage Operations in a Computer        Network”;    -   U.S. Pat. No. 7,315,923, entitled “System And Method For        Combining Data Streams In Pipelined Storage Operations In A        Storage Network”;    -   U.S. Pat. No. 7,343,453, entitled “Hierarchical Systems and        Methods for Providing a Unified View of Storage Information”;    -   U.S. Pat. No. 7,395,282, entitled “Hierarchical Backup and        Retrieval System”;    -   U.S. Pat. No. 7,529,782, entitled “System and Methods for        Performing a Snapshot and for Restoring Data”;    -   U.S. Pat. No. 7,617,262, entitled “System and Methods for        Monitoring Application Data in a Data Replication System”;    -   U.S. Pat. No. 7,734,669, entitled “Managing Copies Of Data”;    -   U.S. Pat. No. 7,747,579, entitled “Metabase for Facilitating        Data Classification”;    -   U.S. Pat. No. 8,156,086, entitled “Systems And Methods For        Stored Data Verification”;    -   U.S. Pat. No. 8,170,995, entitled “Method and System for Offline        Indexing of Content and Classifying Stored Data”;    -   U.S. Pat. No. 8,230,195, entitled “System And Method For        Performing Auxiliary Storage Operations”;    -   U.S. Pat. No. 8,285,681, entitled “Data Object Store and Server        for a Cloud Storage Environment, Including Data Deduplication        and Data Management Across Multiple Cloud Storage Sites”;    -   U.S. Pat. No. 8,307,177, entitled “Systems And Methods For        Management Of Virtualization Data”;    -   U.S. Pat. No. 8,364,652, entitled “Content-Aligned, Block-Based        Deduplication”;    -   U.S. Pat. No. 8,578,120, entitled “Block-Level Single        Instancing”;    -   U.S. Pat. No. 8,954,446, entitled “Client-Side Repository in a        Networked Deduplicated Storage System”;    -   U.S. Pat. No. 9,020,900, entitled “Distributed Deduplicated        Storage System”;    -   U.S. Pat. No. 9,098,495, entitled “Application-Aware and Remote        Single Instance Data Management”;    -   U.S. Pat. No. 9,239,687, entitled “Systems and Methods for        Retaining and Using Data Block Signatures in Data Protection        Operations”;    -   U.S. Pat. No. 9,633,033, entitled “High Availability Distributed        Deduplicated Storage System”;    -   U.S. Pat. No. 9,852,026, entitled “Efficient Application        Recovery based on a Pseudo-Storage-Device Driver”;    -   U.S. Pat. Pub. No. 2006/0224846, entitled “System and Method to        Support Single Instance Storage Operations”;    -   U.S. Pat. Pub. No. 2016-0350391, entitled “Replication Using        Deduplicated Secondary Copy Data”;    -   U.S. Pat. Pub. No. 2017-0168903 A1, entitled “Live        Synchronization and Management of Virtual Machines across        Computing and Virtualization Platforms and Using Live        Synchronization to Support Disaster Recovery”;    -   U.S. Pat. Pub. No. 2017-0185488 A1, entitled “Application-Level        Live Synchronization Across Computing Platforms Including        Synchronizing Co-Resident Applications To Disparate Standby        Destinations And Selectively Synchronizing Some Applications And        Not Others”;    -   U.S. Pat. Pub. No. 2017-0192866 A1, entitled “System For        Redirecting Requests After A Secondary Storage Computing Device        Failure”;    -   U.S. Pat. Pub. No. 2017-0235647 A1, entitled “Data Protection        Operations Based on Network Path Information”; and    -   U.S. Pat. Pub. No. 2017-0242871 A1, entitled “Data Restoration        Operations Based on Network Path Information”.

System 100 includes computing devices and computing technologies. Forinstance, system 100 can include one or more client computing devices102 and secondary storage computing devices 106, as well as storagemanager 140 or a host computing device for it. Computing devices caninclude, without limitation, one or more: workstations, personalcomputers, desktop computers, or other types of generally fixedcomputing systems such as mainframe computers, servers, andminicomputers. Other computing devices can include mobile or portablecomputing devices, such as one or more laptops, tablet computers,personal data assistants, mobile phones (such as smartphones), and othermobile or portable computing devices such as embedded computers, set topboxes, vehicle-mounted devices, wearable computers, etc. Servers caninclude mail servers, file servers, database servers, virtual machineservers, and web servers. Any given computing device comprises one ormore processors (e.g., CPU and/or single-core or multi-core processors),as well as corresponding non-transitory computer memory (e.g.,random-access memory (RAM)) for storing computer programs which are tobe executed by the one or more processors. Other computer memory formass storage of data may be packaged/configured with the computingdevice (e.g., an internal hard disk) and/or may be external andaccessible by the computing device (e.g., network-attached storage, astorage array, etc.). In some cases, a computing device includes cloudcomputing resources, which may be implemented as virtual machines. Forinstance, one or more virtual machines may be provided to theorganization by a third-party cloud service vendor.

In some embodiments, computing devices can include one or more virtualmachine(s) running on a physical host computing device (or “hostmachine”) operated by the organization. As one example, the organizationmay use one virtual machine as a database server and another virtualmachine as a mail server, both virtual machines operating on the samehost machine. A Virtual machine (“VM”) is a software implementation of acomputer that does not physically exist and is instead instantiated inan operating system of a physical computer (or host machine) to enableapplications to execute within the VM's environment, i.e., a VM emulatesa physical computer. AVM includes an operating system and associatedvirtual resources, such as computer memory and processor(s). Ahypervisor operates between the VM and the hardware of the physical hostmachine and is generally responsible for creating and running the VMs.Hypervisors are also known in the art as virtual machine monitors or avirtual machine managers or “VMMs”, and may be implemented in software,firmware, and/or specialized hardware installed on the host machine.Examples of hypervisors include ESX Server, by VMware, Inc. of PaloAlto, Calif.; Microsoft Virtual Server and Microsoft Windows ServerHyper-V, both by Microsoft Corporation of Redmond, Wash.; Sun xVM byOracle America Inc. of Santa Clara, Calif.; and Xen by Citrix Systems,Santa Clara, Calif. The hypervisor provides resources to each virtualoperating system such as a virtual processor, virtual memory, a virtualnetwork device, and a virtual disk. Each virtual machine has one or moreassociated virtual disks. The hypervisor typically stores the data ofvirtual disks in files on the file system of the physical host machine,called virtual machine disk files (“VMDK” in VMware lingo) or virtualhard disk image files (in Microsoft lingo). For example, VMware's ESXServer provides the Virtual Machine File System (VMFS) for the storageof virtual machine disk files. A virtual machine reads data from andwrites data to its virtual disk much the way that a physical machinereads data from and writes data to a physical disk. Examples oftechniques for implementing information management in a cloud computingenvironment are described in U.S. Pat. No. 8,285,681. Examples oftechniques for implementing information management in a virtualizedcomputing environment are described in U.S. Pat. No. 8,307,177.

Information management system 100 can also include electronic datastorage devices, generally used for mass storage of data, including,e.g., primary storage devices 104 and secondary storage devices 108.Storage devices can generally be of any suitable type including, withoutlimitation, disk drives, storage arrays (e.g., storage-area network(SAN) and/or network-attached storage (NAS) technology), semiconductormemory (e.g., solid state storage devices), network attached storage(NAS) devices, tape libraries, or other magnetic, non-tape storagedevices, optical media storage devices, combinations of the same, etc.In some embodiments, storage devices form part of a distributed filesystem. In some cases, storage devices are provided in a cloud storageenvironment (e.g., a private cloud or one operated by a third-partyvendor), whether for primary data or secondary copies or both.

Depending on context, the term “information management system” can referto generally all of the illustrated hardware and software components inFIG. 1C, or the term may refer to only a subset of the illustratedcomponents. For instance, in some cases, system 100 generally refers toa combination of specialized components used to protect, move, manage,manipulate, analyze, and/or process data and metadata generated byclient computing devices 102. However, system 100 in some cases does notinclude the underlying components that generate and/or store primarydata 112, such as the client computing devices 102 themselves, and theprimary storage devices 104. Likewise, secondary storage devices 108(e.g., a third-party provided cloud storage environment) may not be partof system 100. As an example, “information management system” or“storage management system” may sometimes refer to one or more of thefollowing components, which will be described in further detail below:storage manager, data agent, and media agent.

One or more client computing devices 102 may be part of system 100, eachclient computing device 102 having an operating system and at least oneapplication 110 and one or more accompanying data agents executingthereon; and associated with one or more primary storage devices 104storing primary data 112. Client computing device(s) 102 and primarystorage devices 104 may generally be referred to in some cases asprimary storage subsystem 117.

Client Computing Devices, Clients, and Subclients

Typically, a variety of sources in an organization produce data to beprotected and managed. As just one illustrative example, in a corporateenvironment such data sources can be employee workstations and companyservers such as a mail server, a web server, a database server, atransaction server, or the like. In system 100, data generation sourcesinclude one or more client computing devices 102. A computing devicethat has a data agent 142 installed and operating on it is generallyreferred to as a “client computing device” 102, and may include any typeof computing device, without limitation. A client computing device 102may be associated with one or more users and/or user accounts.

A “client” is a logical component of information management system 100,which may represent a logical grouping of one or more data agentsinstalled on a client computing device 102. Storage manager 140recognizes a client as a component of system 100, and in someembodiments, may automatically create a client component the first timea data agent 142 is installed on a client computing device 102. Becausedata generated by executable component(s) 110 is tracked by theassociated data agent 142 so that it may be properly protected in system100, a client may be said to generate data and to store the generateddata to primary storage, such as primary storage device 104. However,the terms “client” and “client computing device” as used herein do notimply that a client computing device 102 is necessarily configured inthe client/server sense relative to another computing device such as amail server, or that a client computing device 102 cannot be a server inits own right. As just a few examples, a client computing device 102 canbe and/or include mail servers, file servers, database servers, virtualmachine servers, and/or web servers.

Each client computing device 102 may have application(s) 110 executingthereon which generate and manipulate the data that is to be protectedfrom loss and managed in system 100. Applications 110 generallyfacilitate the operations of an organization, and can include, withoutlimitation, mail server applications (e.g., Microsoft Exchange Server),file system applications, mail client applications (e.g., MicrosoftExchange Client), database applications or database management systems(e.g., SQL, Oracle, SAP, Lotus Notes Database), word processingapplications (e.g., Microsoft Word), spreadsheet applications, financialapplications, presentation applications, graphics and/or videoapplications, browser applications, mobile applications, entertainmentapplications, and so on. Each application 110 may be accompanied by anapplication-specific data agent 142, though not all data agents 142 areapplication-specific or associated with only application. A file managerapplication, e.g., Microsoft Windows Explorer, may be considered anapplication 110 and may be accompanied by its own data agent 142. Clientcomputing devices 102 can have at least one operating system (e.g.,Microsoft Windows, Mac OS X, iOS, IBM z/OS, Linux, other Unix-basedoperating systems, etc.) installed thereon, which may support or hostone or more file systems and other applications 110. In someembodiments, a virtual machine that executes on a host client computingdevice 102 may be considered an application 110 and may be accompaniedby a specific data agent 142 (e.g., virtual server data agent).

Client computing devices 102 and other components in system 100 can beconnected to one another via one or more electronic communicationpathways 114. For example, a first communication pathway 114 maycommunicatively couple client computing device 102 and secondary storagecomputing device 106; a second communication pathway 114 maycommunicatively couple storage manager 140 and client computing device102; and a third communication pathway 114 may communicatively couplestorage manager 140 and secondary storage computing device 106, etc.(see, e.g., FIG. 1A and FIG. 1C). A communication pathway 114 caninclude one or more networks or other connection types including one ormore of the following, without limitation: the Internet, a wide areanetwork (WAN), a local area network (LAN), a Storage Area Network (SAN),a Fibre Channel (FC) connection, a Small Computer System Interface(SCSI) connection, a virtual private network (VPN), a token ring orTCP/IP based network, an intranet network, a point-to-point link, acellular network, a wireless data transmission system, a two-way cablesystem, an interactive kiosk network, a satellite network, a broadbandnetwork, a baseband network, a neural network, a mesh network, an ad hocnetwork, other appropriate computer or telecommunications networks,combinations of the same or the like. Communication pathways 114 in somecases may also include application programming interfaces (APIs)including, e.g., cloud service provider APIs, virtual machine managementAPIs, and hosted service provider APIs. The underlying infrastructure ofcommunication pathways 114 may be wired and/or wireless, analog and/ordigital, or any combination thereof; and the facilities used may beprivate, public, third-party provided, or any combination thereof,without limitation.

A “subclient” is a logical grouping of all or part of a client's primarydata 112. In general, a subclient may be defined according to how thesubclient data is to be protected as a unit in system 100. For example,a subclient may be associated with a certain storage policy. A givenclient may thus comprise several subclients, each subclient associatedwith a different storage policy. For example, some files may form afirst subclient that requires compression and deduplication and isassociated with a first storage policy. Other files of the client mayform a second subclient that requires a different retention schedule aswell as encryption, and may be associated with a different, secondstorage policy. As a result, though the primary data may be generated bythe same application 110 and may belong to one given client, portions ofthe data may be assigned to different subclients for distinct treatmentby system 100. More detail on subclients is given in regard to storagepolicies below.

Primary Data and Exemplary Primary Storage Devices

Primary data 112 is generally production data or “live” data generatedby the operating system and/or applications 110 executing on clientcomputing device 102. Primary data 112 is generally stored on primarystorage device(s) 104 and is organized via a file system operating onthe client computing device 102. Thus, client computing device(s) 102and corresponding applications 110 may create, access, modify, write,delete, and otherwise use primary data 112. Primary data 112 isgenerally in the native format of the source application 110. Primarydata 112 is an initial or first stored body of data generated by thesource application 110. Primary data 112 in some cases is createdsubstantially directly from data generated by the corresponding sourceapplication 110. It can be useful in performing certain tasks toorganize primary data 112 into units of different granularities. Ingeneral, primary data 112 can include files, directories, file systemvolumes, data blocks, extents, or any other hierarchies or organizationsof data objects. As used herein, a “data object” can refer to (i) anyfile that is currently addressable by a file system or that waspreviously addressable by the file system (e.g., an archive file),and/or to (ii) a subset of such a file (e.g., a data block, an extent,etc.). Primary data 112 may include structured data (e.g., databasefiles), unstructured data (e.g., documents), and/or semi-structureddata. See, e.g., FIG. 1B.

It can also be useful in performing certain functions of system 100 toaccess and modify metadata within primary data 112. Metadata generallyincludes information about data objects and/or characteristicsassociated with the data objects. For simplicity herein, it is to beunderstood that, unless expressly stated otherwise, any reference toprimary data 112 generally also includes its associated metadata, butreferences to metadata generally do not include the primary data.Metadata can include, without limitation, one or more of the following:the data owner (e.g., the client or user that generates the data), thelast modified time (e.g., the time of the most recent modification ofthe data object), a data object name (e.g., a file name), a data objectsize (e.g., a number of bytes of data), information about the content(e.g., an indication as to the existence of a particular search term),user-supplied tags, to/from information for email (e.g., an emailsender, recipient, etc.), creation date, file type (e.g., format orapplication type), last accessed time, application type (e.g., type ofapplication that generated the data object), location/network (e.g., acurrent, past or future location of the data object and network pathwaysto/from the data object), geographic location (e.g., GPS coordinates),frequency of change (e.g., a period in which the data object ismodified), business unit (e.g., a group or department that generates,manages or is otherwise associated with the data object), aginginformation (e.g., a schedule, such as a time period, in which the dataobject is migrated to secondary or long term storage), boot sectors,partition layouts, file location within a file folder directorystructure, user permissions, owners, groups, access control lists(ACLs), system metadata (e.g., registry information), combinations ofthe same or other similar information related to the data object. Inaddition to metadata generated by or related to file systems andoperating systems, some applications 110 and/or other components ofsystem 100 maintain indices of metadata for data objects, e.g., metadataassociated with individual email messages. The use of metadata toperform classification and other functions is described in greaterdetail below.

Primary storage devices 104 storing primary data 112 may be relativelyfast and/or expensive technology (e.g., flash storage, a disk drive, ahard-disk storage array, solid state memory, etc.), typically to supporthigh-performance live production environments. Primary data 112 may behighly changeable and/or may be intended for relatively short termretention (e.g., hours, days, or weeks). According to some embodiments,client computing device 102 can access primary data 112 stored inprimary storage device 104 by making conventional file system calls viathe operating system. Each client computing device 102 is generallyassociated with and/or in communication with one or more primary storagedevices 104 storing corresponding primary data 112. A client computingdevice 102 is said to be associated with or in communication with aparticular primary storage device 104 if it is capable of one or moreof: routing and/or storing data (e.g., primary data 112) to the primarystorage device 104, coordinating the routing and/or storing of data tothe primary storage device 104, retrieving data from the primary storagedevice 104, coordinating the retrieval of data from the primary storagedevice 104, and modifying and/or deleting data in the primary storagedevice 104. Thus, a client computing device 102 may be said to accessdata stored in an associated storage device 104.

Primary storage device 104 may be dedicated or shared. In some cases,each primary storage device 104 is dedicated to an associated clientcomputing device 102, e.g., a local disk drive. In other cases, one ormore primary storage devices 104 can be shared by multiple clientcomputing devices 102, e.g., via a local network, in a cloud storageimplementation, etc. As one example, primary storage device 104 can be astorage array shared by a group of client computing devices 102, such asEMC Clariion, EMC Symmetrix, EMC Celerra, Dell EqualLogic, IBM XIV,NetApp FAS, HP EVA, and HP 3PAR.

System 100 may also include hosted services (not shown), which may behosted in some cases by an entity other than the organization thatemploys the other components of system 100. For instance, the hostedservices may be provided by online service providers. Such serviceproviders can provide social networking services, hosted email services,or hosted productivity applications or other hosted applications such assoftware-as-a-service (SaaS), platform-as-a-service (PaaS), applicationservice providers (ASPs), cloud services, or other mechanisms fordelivering functionality via a network. As it services users, eachhosted service may generate additional data and metadata, which may bemanaged by system 100, e.g., as primary data 112. In some cases, thehosted services may be accessed using one of the applications 110. As anexample, a hosted mail service may be accessed via browser running on aclient computing device 102.

Secondary Copies and Exemplary Secondary Storage Devices

Primary data 112 stored on primary storage devices 104 may becompromised in some cases, such as when an employee deliberately oraccidentally deletes or overwrites primary data 112. Or primary storagedevices 104 can be damaged, lost, or otherwise corrupted. For recoveryand/or regulatory compliance purposes, it is therefore useful togenerate and maintain copies of primary data 112. Accordingly, system100 includes one or more secondary storage computing devices 106 and oneor more secondary storage devices 108 configured to create and store oneor more secondary copies 116 of primary data 112 including itsassociated metadata. The secondary storage computing devices 106 and thesecondary storage devices 108 may be referred to as secondary storagesubsystem 118.

Secondary copies 116 can help in search and analysis efforts and meetother information management goals as well, such as: restoring dataand/or metadata if an original version is lost (e.g., by deletion,corruption, or disaster); allowing point-in-time recovery; complyingwith regulatory data retention and electronic discovery (e-discovery)requirements; reducing utilized storage capacity in the productionsystem and/or in secondary storage; facilitating organization and searchof data; improving user access to data files across multiple computingdevices and/or hosted services; and implementing data retention andpruning policies.

A secondary copy 116 can comprise a separate stored copy of data that isderived from one or more earlier-created stored copies (e.g., derivedfrom primary data 112 or from another secondary copy 116). Secondarycopies 116 can include point-in-time data and may be intended forrelatively long-term retention before some or all of the data is movedto other storage or discarded. In some cases, a secondary copy 116 maybe in a different storage device than other previously stored copies;and/or may be remote from other previously stored copies. Secondarycopies 116 can be stored in the same storage device as primary data 112.For example, a disk array capable of performing hardware snapshotsstores primary data 112 and creates and stores hardware snapshots of theprimary data 112 as secondary copies 116. Secondary copies 116 may bestored in relatively slow and/or lower cost storage (e.g., magnetictape). A secondary copy 116 may be stored in a backup or archive format,or in some other format different from the native source applicationformat or other format of primary data 112.

Secondary storage computing devices 106 may index secondary copies 116(e.g., using a media agent 144), enabling users to browse and restore ata later time and further enabling the lifecycle management of theindexed data. After creation of a secondary copy 116 that representscertain primary data 112, a pointer or other location indicia (e.g., astub) may be placed in primary data 112, or be otherwise associated withprimary data 112, to indicate the current location of a particularsecondary copy 116. Since an instance of a data object or metadata inprimary data 112 may change over time as it is modified by application110 (or hosted service or the operating system), system 100 may createand manage multiple secondary copies 116 of a particular data object ormetadata, each copy representing the state of the data object in primarydata 112 at a particular point in time. Moreover, since an instance of adata object in primary data 112 may eventually be deleted from primarystorage device 104 and the file system, system 100 may continue tomanage point-in-time representations of that data object, even thoughthe instance in primary data 112 no longer exists. For virtual machines,the operating system and other applications 110 of client computingdevice(s) 102 may execute within or under the management ofvirtualization software (e.g., a VMM), and the primary storage device(s)104 may comprise a virtual disk created on a physical storage device.System 100 may create secondary copies 116 of the files or other dataobjects in a virtual disk file and/or secondary copies 116 of the entirevirtual disk file itself (e.g., of an entire .vmdk file).

Secondary copies 116 are distinguishable from corresponding primary data112. First, secondary copies 116 can be stored in a different formatfrom primary data 112 (e.g., backup, archive, or another non-nativeformat). For this or other reasons, secondary copies 116 may not bedirectly usable by applications 110 or client computing device 102(e.g., via standard system calls or otherwise) without modification,processing, or other intervention by system 100 which may be referred toas “restore” operations. Secondary copies 116 may have been processed bydata agent 142 and/or media agent 144 in the course of being created(e.g., compression, deduplication, encryption, integrity markers,indexing, formatting, application-aware metadata, etc.), and thussecondary copy 116 may represent source primary data 112 withoutnecessarily being exactly identical to the source.

Second, secondary copies 116 may be stored on a secondary storage device108 that is inaccessible to application 110 running on client computingdevice 102 and/or hosted service. Some secondary copies 116 may be“offline copies,” in that they are not readily available (e.g., notmounted to tape or disk). Offline copies can include copies of data thatsystem 100 can access without human intervention (e.g., tapes within anautomated tape library, but not yet mounted in a drive), and copies thatthe system 100 can access only with some human intervention (e.g., tapeslocated at an offsite storage site).

Using Intermediate Devices for Creating Secondary Copies—SecondaryStorage Computing Devices

Creating secondary copies can be challenging when hundreds or thousandsof client computing devices 102 continually generate large volumes ofprimary data 112 to be protected. Also, there can be significantoverhead involved in the creation of secondary copies 116. Moreover,specialized programmed intelligence and/or hardware capability isgenerally needed for accessing and interacting with secondary storagedevices 108. Client computing devices 102 may interact directly with asecondary storage device 108 to create secondary copies 116, but in viewof the factors described above, this approach can negatively impact theability of client computing device 102 to serve/service application 110and produce primary data 112. Further, any given client computing device102 may not be optimized for interaction with certain secondary storagedevices 108.

Thus, system 100 may include one or more software and/or hardwarecomponents which generally act as intermediaries between clientcomputing devices 102 (that generate primary data 112) and secondarystorage devices 108 (that store secondary copies 116). In addition tooff-loading certain responsibilities from client computing devices 102,these intermediate components provide other benefits. For instance, asdiscussed further below with respect to FIG. 1D, distributing some ofthe work involved in creating secondary copies 116 can enhancescalability and improve system performance. For instance, usingspecialized secondary storage computing devices 106 and media agents 144for interfacing with secondary storage devices 108 and/or for performingcertain data processing operations can greatly improve the speed withwhich system 100 performs information management operations and can alsoimprove the capacity of the system to handle large numbers of suchoperations, while reducing the computational load on the productionenvironment of client computing devices 102. The intermediate componentscan include one or more secondary storage computing devices 106 as shownin FIG. 1A and/or one or more media agents 144. Media agents arediscussed further below (e.g., with respect to FIGS. 1C-1E). Thesespecial-purpose components of system 100 comprise specialized programmedintelligence and/or hardware capability for writing to, reading from,instructing, communicating with, or otherwise interacting with secondarystorage devices 108.

Secondary storage computing device(s) 106 can comprise any of thecomputing devices described above, without limitation. In some cases,secondary storage computing device(s) 106 also include specializedhardware componentry and/or software intelligence (e.g., specializedinterfaces) for interacting with certain secondary storage device(s) 108with which they may be specially associated.

To create a secondary copy 116 involving the copying of data fromprimary storage subsystem 117 to secondary storage subsystem 118, clientcomputing device 102 may communicate the primary data 112 to be copied(or a processed version thereof generated by a data agent 142) to thedesignated secondary storage computing device 106, via a communicationpathway 114. Secondary storage computing device 106 in turn may furtherprocess and convey the data or a processed version thereof to secondarystorage device 108. One or more secondary copies 116 may be created fromexisting secondary copies 116, such as in the case of an auxiliary copyoperation, described further below.

Exemplary Primary Data and an Exemplary Secondary Copy

FIG. 1B is a detailed view of some specific examples of primary datastored on primary storage device(s) 104 and secondary copy data storedon secondary storage device(s) 108, with other components of the systemremoved for the purposes of illustration. Stored on primary storagedevice(s) 104 are primary data 112 objects including word processingdocuments 119A-B, spreadsheets 120, presentation documents 122, videofiles 124, image files 126, email mailboxes 128 (and corresponding emailmessages 129A-C), HTML/XML or other types of markup language files 130,databases 132 and corresponding tables or other data structures133A-133C. Some or all primary data 112 objects are associated withcorresponding metadata (e.g., “Meta1-11”), which may include file systemmetadata and/or application-specific metadata. Stored on the secondarystorage device(s) 108 are secondary copy 116 data objects 134A-C whichmay include copies of or may otherwise represent corresponding primarydata 112.

Secondary copy data objects 134A-C can individually represent more thanone primary data object. For example, secondary copy data object 134Arepresents three separate primary data objects 133C, 122, and 129C(represented as 133C′, 122′, and 129C′, respectively, and accompanied bycorresponding metadata Meta11, Meta3, and Meta8, respectively).Moreover, as indicated by the prime mark (′), secondary storagecomputing devices 106 or other components in secondary storage subsystem118 may process the data received from primary storage subsystem 117 andstore a secondary copy including a transformed and/or supplementedrepresentation of a primary data object and/or metadata that isdifferent from the original format, e.g., in a compressed, encrypted,deduplicated, or other modified format. For instance, secondary storagecomputing devices 106 can generate new metadata or other informationbased on said processing and store the newly generated information alongwith the secondary copies. Secondary copy data object 1346 representsprimary data objects 120, 1336, and 119A as 120′, 1336′, and 119A′,respectively, accompanied by corresponding metadata Meta2, Meta10, andMeta1, respectively. Also, secondary copy data object 134C representsprimary data objects 133A, 1196, and 129A as 133A′, 1196′, and 129A′,respectively, accompanied by corresponding metadata Meta9, Meta5, andMeta6, respectively.

Exemplary Information Management System Architecture

System 100 can incorporate a variety of different hardware and softwarecomponents, which can in turn be organized with respect to one anotherin many different configurations, depending on the embodiment. There arecritical design choices involved in specifying the functionalresponsibilities of the components and the role of each component insystem 100. Such design choices can impact how system 100 performs andadapts to data growth and other changing circumstances. FIG. 1C shows asystem 100 designed according to these considerations and includes:storage manager 140, one or more data agents 142 executing on clientcomputing device(s) 102 and configured to process primary data 112, andone or more media agents 144 executing on one or more secondary storagecomputing devices 106 for performing tasks involving secondary storagedevices 108.

Storage Manager

Storage manager 140 is a centralized storage and/or information managerthat is configured to perform certain control functions and also tostore certain critical information about system 100—hence storagemanager 140 is said to manage system 100. As noted, the number ofcomponents in system 100 and the amount of data under management can belarge. Managing the components and data is therefore a significant task,which can grow unpredictably as the number of components and data scaleto meet the needs of the organization. For these and other reasons,according to certain embodiments, responsibility for controlling system100, or at least a significant portion of that responsibility, isallocated to storage manager 140. Storage manager 140 can be adaptedindependently according to changing circumstances, without having toreplace or re-design the remainder of the system. Moreover, a computingdevice for hosting and/or operating as storage manager 140 can beselected to best suit the functions and networking needs of storagemanager 140. These and other advantages are described in further detailbelow and with respect to FIG. 1D.

Storage manager 140 may be a software module or other application hostedby a suitable computing device. In some embodiments, storage manager 140is itself a computing device that performs the functions describedherein. Storage manager 140 comprises or operates in conjunction withone or more associated data structures such as a dedicated database(e.g., management database 146), depending on the configuration. Thestorage manager 140 generally initiates, performs, coordinates, and/orcontrols storage and other information management operations performedby system 100, e.g., to protect and control primary data 112 andsecondary copies 116. In general, storage manager 140 is said to managesystem 100, which includes communicating with, instructing, andcontrolling in some circumstances components such as data agents 142 andmedia agents 144, etc.

As shown by the dashed arrowed lines 114 in FIG. 1C, storage manager 140may communicate with, instruct, and/or control some or all elements ofsystem 100, such as data agents 142 and media agents 144. In thismanner, storage manager 140 manages the operation of various hardwareand software components in system 100. In certain embodiments, controlinformation originates from storage manager 140 and status as well asindex reporting is transmitted to storage manager 140 by the managedcomponents, whereas payload data and metadata are generally communicatedbetween data agents 142 and media agents 144 (or otherwise betweenclient computing device(s) 102 and secondary storage computing device(s)106), e.g., at the direction of and under the management of storagemanager 140. Control information can generally include parameters andinstructions for carrying out information management operations, suchas, without limitation, instructions to perform a task associated withan operation, timing information specifying when to initiate a task,data path information specifying what components to communicate with oraccess in carrying out an operation, and the like. In other embodiments,some information management operations are controlled or initiated byother components of system 100 (e.g., by media agents 144 or data agents142), instead of or in combination with storage manager 140.

According to certain embodiments, storage manager 140 provides one ormore of the following functions:

-   -   communicating with data agents 142 and media agents 144,        including transmitting instructions, messages, and/or queries,        as well as receiving status reports, index information,        messages, and/or queries, and responding to same;    -   initiating execution of information management operations;    -   initiating restore and recovery operations;    -   managing secondary storage devices 108 and inventory/capacity of        the same;    -   allocating secondary storage devices 108 for secondary copy        operations;    -   reporting, searching, and/or classification of data in system        100;    -   monitoring completion of and status reporting related to        information management operations and jobs;    -   tracking movement of data within system 100;    -   tracking age information relating to secondary copies 116,        secondary storage devices 108, comparing the age information        against retention guidelines, and initiating data pruning when        appropriate;    -   tracking logical associations between components in system 100;    -   protecting metadata associated with system 100, e.g., in        management database 146;    -   implementing job management, schedule management, event        management, alert management, reporting, job history        maintenance, user security management, disaster recovery        management, and/or user interfacing for system administrators        and/or end users of system 100;    -   sending, searching, and/or viewing of log files; and    -   implementing operations management functionality.

Storage manager 140 may maintain an associated database 146 (or “storagemanager database 146” or “management database 146”) ofmanagement-related data and information management policies 148.Database 146 is stored in computer memory accessible by storage manager140. Database 146 may include a management index 150 (or “index 150”) orother data structure(s) that may store: logical associations betweencomponents of the system; user preferences and/or profiles (e.g.,preferences regarding encryption, compression, or deduplication ofprimary data or secondary copies; preferences regarding the scheduling,type, or other aspects of secondary copy or other operations; mappingsof particular information management users or user accounts to certaincomputing devices or other components, etc.; management tasks; mediacontainerization; other useful data; and/or any combination thereof. Forexample, storage manager 140 may use index 150 to track logicalassociations between media agents 144 and secondary storage devices 108and/or movement of data to/from secondary storage devices 108. Forinstance, index 150 may store data associating a client computing device102 with a particular media agent 144 and/or secondary storage device108, as specified in an information management policy 148.

Administrators and others may configure and initiate certain informationmanagement operations on an individual basis. But while this may beacceptable for some recovery operations or other infrequent tasks, it isoften not workable for implementing on-going organization-wide dataprotection and management. Thus, system 100 may utilize informationmanagement policies 148 for specifying and executing informationmanagement operations on an automated basis. Generally, an informationmanagement policy 148 can include a stored data structure or otherinformation source that specifies parameters (e.g., criteria and rules)associated with storage management or other information managementoperations. Storage manager 140 can process an information managementpolicy 148 and/or index 150 and, based on the results, identify aninformation management operation to perform, identify the appropriatecomponents in system 100 to be involved in the operation (e.g., clientcomputing devices 102 and corresponding data agents 142, secondarystorage computing devices 106 and corresponding media agents 144, etc.),establish connections to those components and/or between thosecomponents, and/or instruct and control those components to carry outthe operation. In this manner, system 100 can translate storedinformation into coordinated activity among the various computingdevices in system 100.

Management database 146 may maintain information management policies 148and associated data, although information management policies 148 can bestored in computer memory at any appropriate location outside managementdatabase 146. For instance, an information management policy 148 such asa storage policy may be stored as metadata in a media agent database 152or in a secondary storage device 108 (e.g., as an archive copy) for usein restore or other information management operations, depending on theembodiment. Information management policies 148 are described furtherbelow. According to certain embodiments, management database 146comprises a relational database (e.g., an SQL database) for trackingmetadata, such as metadata associated with secondary copy operations(e.g., what client computing devices 102 and corresponding subclientdata were protected and where the secondary copies are stored and whichmedia agent 144 performed the storage operation(s)). This and othermetadata may additionally be stored in other locations, such as atsecondary storage computing device 106 or on the secondary storagedevice 108, allowing data recovery without the use of storage manager140 in some cases. Thus, management database 146 may comprise dataneeded to kick off secondary copy operations (e.g., storage policies,schedule policies, etc.), status and reporting information aboutcompleted jobs (e.g., status and error reports on yesterday's backupjobs), and additional information sufficient to enable restore anddisaster recovery operations (e.g., media agent associations, locationindexing, content indexing, etc.).

Storage manager 140 may include a jobs agent 156, a user interface 158,and a management agent 154, all of which may be implemented asinterconnected software modules or application programs. These aredescribed further below.

Jobs agent 156 in some embodiments initiates, controls, and/or monitorsthe status of some or all information management operations previouslyperformed, currently being performed, or scheduled to be performed bysystem 100. A job is a logical grouping of information managementoperations such as daily storage operations scheduled for a certain setof subclients (e.g., generating incremental block-level backup copies116 at a certain time every day for database files in a certaingeographical location). Thus, jobs agent 156 may access informationmanagement policies 148 (e.g., in management database 146) to determinewhen, where, and how to initiate/control jobs in system 100.

Storage Manager User Interfaces

User interface 158 may include information processing and displaysoftware, such as a graphical user interface (GUI), an applicationprogram interface (API), and/or other interactive interface(s) throughwhich users and system processes can retrieve information about thestatus of information management operations or issue instructions tostorage manager 140 and other components. Via user interface 158, usersmay issue instructions to the components in system 100 regardingperformance of secondary copy and recovery operations. For example, auser may modify a schedule concerning the number of pending secondarycopy operations. As another example, a user may employ the GUI to viewthe status of pending secondary copy jobs or to monitor the status ofcertain components in system 100 (e.g., the amount of capacity left in astorage device). Storage manager 140 may track information that permitsit to select, designate, or otherwise identify content indices,deduplication databases, or similar databases or resources or data setswithin its information management cell (or another cell) to be searchedin response to certain queries. Such queries may be entered by the userby interacting with user interface 158.

Various embodiments of information management system 100 may beconfigured and/or designed to generate user interface data usable forrendering the various interactive user interfaces described. The userinterface data may be used by system 100 and/or by another system,device, and/or software program (for example, a browser program), torender the interactive user interfaces. The interactive user interfacesmay be displayed on, for example, electronic displays (including, forexample, touch-enabled displays), consoles, etc., whetherdirect-connected to storage manager 140 or communicatively coupledremotely, e.g., via an internet connection. The present disclosuredescribes various embodiments of interactive and dynamic userinterfaces, some of which may be generated by user interface agent 158,and which are the result of significant technological development. Theuser interfaces described herein may provide improved human-computerinteractions, allowing for significant cognitive and ergonomicefficiencies and advantages over previous systems, including reducedmental workloads, improved decision-making, and the like. User interface158 may operate in a single integrated view or console (not shown). Theconsole may support a reporting capability for generating a variety ofreports, which may be tailored to a particular aspect of informationmanagement.

User interfaces are not exclusive to storage manager 140 and in someembodiments a user may access information locally from a computingdevice component of system 100. For example, some information pertainingto installed data agents 142 and associated data streams may beavailable from client computing device 102. Likewise, some informationpertaining to media agents 144 and associated data streams may beavailable from secondary storage computing device 106.

Storage Manager Management Agent

Management agent 154 can provide storage manager 140 with the ability tocommunicate with other components within system 100 and/or with otherinformation management cells via network protocols and applicationprogramming interfaces (APIs) including, e.g., HTTP, HTTPS, FTP, REST,virtualization software APIs, cloud service provider APIs, and hostedservice provider APIs, without limitation. Management agent 154 alsoallows multiple information management cells to communicate with oneanother. For example, system 100 in some cases may be one informationmanagement cell in a network of multiple cells adjacent to one anotheror otherwise logically related, e.g., in a WAN or LAN. With thisarrangement, the cells may communicate with one another throughrespective management agents 154. Inter-cell communications andhierarchy is described in greater detail in e.g., U.S. Pat. No.7,343,453.

Information Management Cell

An “information management cell” (or “storage operation cell” or “cell”)may generally include a logical and/or physical grouping of acombination of hardware and software components associated withperforming information management operations on electronic data,typically one storage manager 140 and at least one data agent 142(executing on a client computing device 102) and at least one mediaagent 144 (executing on a secondary storage computing device 106). Forinstance, the components shown in FIG. 1C may together form aninformation management cell. Thus, in some configurations, a system 100may be referred to as an information management cell or a storageoperation cell. A given cell may be identified by the identity of itsstorage manager 140, which is generally responsible for managing thecell.

Multiple cells may be organized hierarchically, so that cells mayinherit properties from hierarchically superior cells or be controlledby other cells in the hierarchy (automatically or otherwise).Alternatively, in some embodiments, cells may inherit or otherwise beassociated with information management policies, preferences,information management operational parameters, or other properties orcharacteristics according to their relative position in a hierarchy ofcells. Cells may also be organized hierarchically according to function,geography, architectural considerations, or other factors useful ordesirable in performing information management operations. For example,a first cell may represent a geographic segment of an enterprise, suchas a Chicago office, and a second cell may represent a differentgeographic segment, such as a New York City office. Other cells mayrepresent departments within a particular office, e.g., human resources,finance, engineering, etc. Where delineated by function, a first cellmay perform one or more first types of information management operations(e.g., one or more first types of secondary copies at a certainfrequency), and a second cell may perform one or more second types ofinformation management operations (e.g., one or more second types ofsecondary copies at a different frequency and under different retentionrules). In general, the hierarchical information is maintained by one ormore storage managers 140 that manage the respective cells (e.g., incorresponding management database(s) 146).

Data Agents

A variety of different applications 110 can operate on a given clientcomputing device 102, including operating systems, file systems,database applications, e-mail applications, and virtual machines, justto name a few. And, as part of the process of creating and restoringsecondary copies 116, the client computing device 102 may be tasked withprocessing and preparing the primary data 112 generated by these variousapplications 110. Moreover, the nature of the processing/preparation candiffer across application types, e.g., due to inherent structural,state, and formatting differences among applications 110 and/or theoperating system of client computing device 102. Each data agent 142 istherefore advantageously configured in some embodiments to assist in theperformance of information management operations based on the type ofdata that is being protected at a client-specific and/orapplication-specific level.

Data agent 142 is a component of information system 100 and is generallydirected by storage manager 140 to participate in creating or restoringsecondary copies 116. Data agent 142 may be a software program (e.g., inthe form of a set of executable binary files) that executes on the sameclient computing device 102 as the associated application 110 that dataagent 142 is configured to protect. Data agent 142 is generallyresponsible for managing, initiating, or otherwise assisting in theperformance of information management operations in reference to itsassociated application(s) 110 and corresponding primary data 112 whichis generated/accessed by the particular application(s) 110. Forinstance, data agent 142 may take part in copying, archiving, migrating,and/or replicating of certain primary data 112 stored in the primarystorage device(s) 104. Data agent 142 may receive control informationfrom storage manager 140, such as commands to transfer copies of dataobjects and/or metadata to one or more media agents 144. Data agent 142also may compress, deduplicate, and encrypt certain primary data 112, aswell as capture application-related metadata before transmitting theprocessed data to media agent 144. Data agent 142 also may receiveinstructions from storage manager 140 to restore (or assist inrestoring) a secondary copy 116 from secondary storage device 108 toprimary storage 104, such that the restored data may be properlyaccessed by application 110 in a suitable format as though it wereprimary data 112.

Each data agent 142 may be specialized for a particular application 110.For instance, different individual data agents 142 may be designed tohandle Microsoft Exchange data, Lotus Notes data, Microsoft Windows filesystem data, Microsoft Active Directory Objects data, SQL Server data,SharePoint data, Oracle database data, SAP database data, virtualmachines and/or associated data, and other types of data. A file systemdata agent, for example, may handle data files and/or other file systeminformation. If a client computing device 102 has two or more types ofdata 112, a specialized data agent 142 may be used for each data type.For example, to backup, migrate, and/or restore all of the data on aMicrosoft Exchange server, the client computing device 102 may use: (1)a Microsoft Exchange Mailbox data agent 142 to back up the Exchangemailboxes; (2) a Microsoft Exchange Database data agent 142 to back upthe Exchange databases; (3) a Microsoft Exchange Public Folder dataagent 142 to back up the Exchange Public Folders; and (4) a MicrosoftWindows File System data agent 142 to back up the file system of clientcomputing device 102. In this example, these specialized data agents 142are treated as four separate data agents 142 even though they operate onthe same client computing device 102. Other examples may include archivemanagement data agents such as a migration archiver or a compliancearchiver, Quick Recovery® agents, and continuous data replicationagents. Application-specific data agents 142 can provide improvedperformance as compared to generic agents. For instance, becauseapplication-specific data agents 142 may only handle data for a singlesoftware application, the design, operation, and performance of the dataagent 142 can be streamlined. The data agent 142 may therefore executefaster and consume less persistent storage and/or operating memory thandata agents designed to generically accommodate multiple differentsoftware applications 110.

Each data agent 142 may be configured to access data and/or metadatastored in the primary storage device(s) 104 associated with data agent142 and its host client computing device 102 and process the dataappropriately. For example, during a secondary copy operation, dataagent 142 may arrange or assemble the data and metadata into one or morefiles having a certain format (e.g., a particular backup or archiveformat) before transferring the file(s) to a media agent 144 or anothercomponent. The file(s) may include a list of files or other metadata. Insome embodiments, a data agent 142 may be distributed between clientcomputing device 102 and storage manager 140 (and any other intermediatecomponents) or may be deployed from a remote location or its functionsapproximated by a remote process that performs some or all of thefunctions of data agent 142. In addition, a data agent 142 may performsome functions provided by media agent 144. Other embodiments may employone or more generic data agents 142 that can handle and process datafrom two or more different applications 110, or that can handle andprocess multiple data types, instead of or in addition to usingspecialized data agents 142. For example, one generic data agent 142 maybe used to back up, migrate and restore Microsoft Exchange Mailbox dataand Microsoft Exchange Database data, while another generic data agentmay handle Microsoft Exchange Public Folder data and Microsoft WindowsFile System data.

Media Agents

As noted, off-loading certain responsibilities from client computingdevices 102 to intermediate components such as secondary storagecomputing device(s) 106 and corresponding media agent(s) 144 can providea number of benefits including improved performance of client computingdevice 102, faster and more reliable information management operations,and enhanced scalability. In one example which will be discussed furtherbelow, media agent 144 can act as a local cache of recently-copied dataand/or metadata stored to secondary storage device(s) 108, thusimproving restore capabilities and performance for the cached data.

Media agent 144 is a component of system 100 and is generally directedby storage manager 140 in creating and restoring secondary copies 116.Whereas storage manager 140 generally manages system 100 as a whole,media agent 144 provides a portal to certain secondary storage devices108, such as by having specialized features for communicating with andaccessing certain associated secondary storage device 108. Media agent144 may be a software program (e.g., in the form of a set of executablebinary files) that executes on a secondary storage computing device 106.Media agent 144 generally manages, coordinates, and facilitates thetransmission of data between a data agent 142 (executing on clientcomputing device 102) and secondary storage device(s) 108 associatedwith media agent 144. For instance, other components in the system mayinteract with media agent 144 to gain access to data stored onassociated secondary storage device(s) 108, (e.g., to browse, read,write, modify, delete, or restore data). Moreover, media agents 144 cangenerate and store information relating to characteristics of the storeddata and/or metadata, or can generate and store other types ofinformation that generally provides insight into the contents of thesecondary storage devices 108—generally referred to as indexing of thestored secondary copies 116. Each media agent 144 may operate on adedicated secondary storage computing device 106, while in otherembodiments a plurality of media agents 144 may operate on the samesecondary storage computing device 106.

A media agent 144 may be associated with a particular secondary storagedevice 108 if that media agent 144 is capable of one or more of: routingand/or storing data to the particular secondary storage device 108;coordinating the routing and/or storing of data to the particularsecondary storage device 108; retrieving data from the particularsecondary storage device 108; coordinating the retrieval of data fromthe particular secondary storage device 108; and modifying and/ordeleting data retrieved from the particular secondary storage device108. Media agent 144 in certain embodiments is physically separate fromthe associated secondary storage device 108. For instance, a media agent144 may operate on a secondary storage computing device 106 in adistinct housing, package, and/or location from the associated secondarystorage device 108. In one example, a media agent 144 operates on afirst server computer and is in communication with a secondary storagedevice(s) 108 operating in a separate rack-mounted RAID-based system.

A media agent 144 associated with a particular secondary storage device108 may instruct secondary storage device 108 to perform an informationmanagement task. For instance, a media agent 144 may instruct a tapelibrary to use a robotic arm or other retrieval means to load or eject acertain backup media, and to subsequently archive, migrate, or retrievedata to or from that media, e.g., for the purpose of restoring data to aclient computing device 102. As another example, a secondary storagedevice 108 may include an array of hard disk drives or solid statedrives organized in a RAID configuration, and media agent 144 mayforward a logical unit number (LUN) and other appropriate information tothe array, which uses the received information to execute the desiredsecondary copy operation. Media agent 144 may communicate with asecondary storage device 108 via a suitable communications link, such asa SCSI or Fibre Channel link.

Each media agent 144 may maintain an associated media agent database152. Media agent database 152 may be stored to a disk or other storagedevice (not shown) that is local to the secondary storage computingdevice 106 on which media agent 144 executes. In other cases, mediaagent database 152 is stored separately from the host secondary storagecomputing device 106. Media agent database 152 can include, among otherthings, a media agent index 153 (see, e.g., FIG. 1C). In some cases,media agent index 153 does not form a part of and is instead separatefrom media agent database 152.

Media agent index 153 (or “index 153”) may be a data structureassociated with the particular media agent 144 that includes informationabout the stored data associated with the particular media agent andwhich may be generated in the course of performing a secondary copyoperation or a restore. Index 153 provides a fast and efficientmechanism for locating/browsing secondary copies 116 or other datastored in secondary storage devices 108 without having to accesssecondary storage device 108 to retrieve the information from there. Forinstance, for each secondary copy 116, index 153 may include metadatasuch as a list of the data objects (e.g., files/subdirectories, databaseobjects, mailbox objects, etc.), a logical path to the secondary copy116 on the corresponding secondary storage device 108, locationinformation (e.g., offsets) indicating where the data objects are storedin the secondary storage device 108, when the data objects were createdor modified, etc. Thus, index 153 includes metadata associated with thesecondary copies 116 that is readily available for use from media agent144. In some embodiments, some or all of the information in index 153may instead or additionally be stored along with secondary copies 116 insecondary storage device 108. In some embodiments, a secondary storagedevice 108 can include sufficient information to enable a “bare metalrestore,” where the operating system and/or software applications of afailed client computing device 102 or another target may beautomatically restored without manually reinstalling individual softwarepackages (including operating systems).

Because index 153 may operate as a cache, it can also be referred to asan “index cache.” In such cases, information stored in index cache 153typically comprises data that reflects certain particulars aboutrelatively recent secondary copy operations. After some triggeringevent, such as after some time elapses or index cache 153 reaches aparticular size, certain portions of index cache 153 may be copied ormigrated to secondary storage device 108, e.g., on a least-recently-usedbasis. This information may be retrieved and uploaded back into indexcache 153 or otherwise restored to media agent 144 to facilitateretrieval of data from the secondary storage device(s) 108. In someembodiments, the cached information may include format orcontainerization information related to archives or other files storedon storage device(s) 108.

In some alternative embodiments media agent 144 generally acts as acoordinator or facilitator of secondary copy operations between clientcomputing devices 102 and secondary storage devices 108, but does notactually write the data to secondary storage device 108. For instance,storage manager 140 (or media agent 144) may instruct a client computingdevice 102 and secondary storage device 108 to communicate with oneanother directly. In such a case, client computing device 102 transmitsdata directly or via one or more intermediary components to secondarystorage device 108 according to the received instructions, and viceversa. Media agent 144 may still receive, process, and/or maintainmetadata related to the secondary copy operations, i.e., may continue tobuild and maintain index 153. In these embodiments, payload data canflow through media agent 144 for the purposes of populating index 153,but not for writing to secondary storage device 108. Media agent 144and/or other components such as storage manager 140 may in some casesincorporate additional functionality, such as data classification,content indexing, deduplication, encryption, compression, and the like.Further details regarding these and other functions are described below.

Distributed, Scalable Architecture

As described, certain functions of system 100 can be distributed amongstvarious physical and/or logical components. For instance, one or more ofstorage manager 140, data agents 142, and media agents 144 may operateon computing devices that are physically separate from one another. Thisarchitecture can provide a number of benefits. For instance, hardwareand software design choices for each distributed component can betargeted to suit its particular function. The secondary computingdevices 106 on which media agents 144 operate can be tailored forinteraction with associated secondary storage devices 108 and providefast index cache operation, among other specific tasks. Similarly,client computing device(s) 102 can be selected to effectively serviceapplications 110 in order to efficiently produce and store primary data112.

Moreover, in some cases, one or more of the individual components ofinformation management system 100 can be distributed to multipleseparate computing devices. As one example, for large file systems wherethe amount of data stored in management database 146 is relativelylarge, database 146 may be migrated to or may otherwise reside on aspecialized database server (e.g., an SQL server) separate from a serverthat implements the other functions of storage manager 140. Thisdistributed configuration can provide added protection because database146 can be protected with standard database utilities (e.g., SQL logshipping or database replication) independent from other functions ofstorage manager 140. Database 146 can be efficiently replicated to aremote site for use in the event of a disaster or other data loss at theprimary site. Or database 146 can be replicated to another computingdevice within the same site, such as to a higher performance machine inthe event that a storage manager host computing device can no longerservice the needs of a growing system 100.

The distributed architecture also provides scalability and efficientcomponent utilization. FIG. 1D shows an embodiment of informationmanagement system 100 including a plurality of client computing devices102 and associated data agents 142 as well as a plurality of secondarystorage computing devices 106 and associated media agents 144.Additional components can be added or subtracted based on the evolvingneeds of system 100. For instance, depending on where bottlenecks areidentified, administrators can add additional client computing devices102, secondary storage computing devices 106, and/or secondary storagedevices 108. Moreover, where multiple fungible components are available,load balancing can be implemented to dynamically address identifiedbottlenecks. As an example, storage manager 140 may dynamically selectwhich media agents 144 and/or secondary storage devices 108 to use forstorage operations based on a processing load analysis of media agents144 and/or secondary storage devices 108, respectively.

Where system 100 includes multiple media agents 144 (see, e.g., FIG.1D), a first media agent 144 may provide failover functionality for asecond failed media agent 144. In addition, media agents 144 can bedynamically selected to provide load balancing. Each client computingdevice 102 can communicate with, among other components, any of themedia agents 144, e.g., as directed by storage manager 140. And eachmedia agent 144 may communicate with, among other components, any ofsecondary storage devices 108, e.g., as directed by storage manager 140.Thus, operations can be routed to secondary storage devices 108 in adynamic and highly flexible manner, to provide load balancing, failover,etc. Further examples of scalable systems capable of dynamic storageoperations, load balancing, and failover are provided in U.S. Pat. No.7,246,207.

While distributing functionality amongst multiple computing devices canhave certain advantages, in other contexts it can be beneficial toconsolidate functionality on the same computing device. In alternativeconfigurations, certain components may reside and execute on the samecomputing device. As such, in other embodiments, one or more of thecomponents shown in FIG. 1C may be implemented on the same computingdevice. In one configuration, a storage manager 140, one or more dataagents 142, and/or one or more media agents 144 are all implemented onthe same computing device. In other embodiments, one or more data agents142 and one or more media agents 144 are implemented on the samecomputing device, while storage manager 140 is implemented on a separatecomputing device, etc. without limitation.

Exemplary Types of Information Management Operations, Including StorageOperations

In order to protect and leverage stored data, system 100 can beconfigured to perform a variety of information management operations,which may also be referred to in some cases as storage managementoperations or storage operations. These operations can generally include(i) data movement operations, (ii) processing and data manipulationoperations, and (iii) analysis, reporting, and management operations.

Data Movement Operations, Including Secondary Copy Operations

Data movement operations are generally storage operations that involvethe copying or migration of data between different locations in system100. For example, data movement operations can include operations inwhich stored data is copied, migrated, or otherwise transferred from oneor more first storage devices to one or more second storage devices,such as from primary storage device(s) 104 to secondary storagedevice(s) 108, from secondary storage device(s) 108 to differentsecondary storage device(s) 108, from secondary storage devices 108 toprimary storage devices 104, or from primary storage device(s) 104 todifferent primary storage device(s) 104, or in some cases within thesame primary storage device 104 such as within a storage array.

Data movement operations can include by way of example, backupoperations, archive operations, information lifecycle managementoperations such as hierarchical storage management operations,replication operations (e.g., continuous data replication), snapshotoperations, deduplication or single-instancing operations, auxiliarycopy operations, disaster-recovery copy operations, and the like. Aswill be discussed, some of these operations do not necessarily createdistinct copies. Nonetheless, some or all of these operations aregenerally referred to as “secondary copy operations” for simplicity,because they involve secondary copies. Data movement also comprisesrestoring secondary copies.

Backup Operations

A backup operation creates a copy of a version of primary data 112 at aparticular point in time (e.g., one or more files or other data units).Each subsequent backup copy 116 (which is a form of secondary copy 116)may be maintained independently of the first. A backup generallyinvolves maintaining a version of the copied primary data 112 as well asbackup copies 116. Further, a backup copy in some embodiments isgenerally stored in a form that is different from the native format,e.g., a backup format. This contrasts to the version in primary data 112which may instead be stored in a format native to the sourceapplication(s) 110. In various cases, backup copies can be stored in aformat in which the data is compressed, encrypted, deduplicated, and/orotherwise modified from the original native application format. Forexample, a backup copy may be stored in a compressed backup format thatfacilitates efficient long-term storage. Backup copies 116 can haverelatively long retention periods as compared to primary data 112, whichis generally highly changeable. Backup copies 116 may be stored on mediawith slower retrieval times than primary storage device 104. Some backupcopies may have shorter retention periods than some other types ofsecondary copies 116, such as archive copies (described below). Backupsmay be stored at an offsite location.

Backup operations can include full backups, differential backups,incremental backups, “synthetic full” backups, and/or creating a“reference copy.” A full backup (or “standard full backup”) in someembodiments is generally a complete image of the data to be protected.However, because full backup copies can consume a relatively largeamount of storage, it can be useful to use a full backup copy as abaseline and only store changes relative to the full backup copyafterwards.

A differential backup operation (or cumulative incremental backupoperation) tracks and stores changes that occurred since the last fullbackup. Differential backups can grow quickly in size, but can restorerelatively efficiently because a restore can be completed in some casesusing only the full backup copy and the latest differential copy.

An incremental backup operation generally tracks and stores changessince the most recent backup copy of any type, which can greatly reducestorage utilization. In some cases, however, restoring can be lengthycompared to full or differential backups because completing a restoreoperation may involve accessing a full backup in addition to multipleincremental backups.

Synthetic full backups generally consolidate data without directlybacking up data from the client computing device. A synthetic fullbackup is created from the most recent full backup (i.e., standard orsynthetic) and subsequent incremental and/or differential backups. Theresulting synthetic full backup is identical to what would have beencreated had the last backup for the subclient been a standard fullbackup. Unlike standard full, incremental, and differential backups,however, a synthetic full backup does not actually transfer data fromprimary storage to the backup media, because it operates as a backupconsolidator. A synthetic full backup extracts the index data of eachparticipating subclient. Using this index data and the previously backedup user data images, it builds new full backup images (e.g., bitmaps),one for each subclient. The new backup images consolidate the index anduser data stored in the related incremental, differential, and previousfull backups into a synthetic backup file that fully represents thesubclient (e.g., via pointers) but does not comprise all its constituentdata.

Any of the above types of backup operations can be at the volume level,file level, or block level. Volume level backup operations generallyinvolve copying of a data volume (e.g., a logical disk or partition) asa whole. In a file-level backup, information management system 100generally tracks changes to individual files and includes copies offiles in the backup copy. For block-level backups, files are broken intoconstituent blocks, and changes are tracked at the block level. Uponrestore, system 100 reassembles the blocks into files in a transparentfashion. Far less data may actually be transferred and copied tosecondary storage devices 108 during a file-level copy than avolume-level copy. Likewise, a block-level copy may transfer less datathan a file-level copy, resulting in faster execution. However,restoring a relatively higher-granularity copy can result in longerrestore times. For instance, when restoring a block-level copy, theprocess of locating and retrieving constituent blocks can sometimes takelonger than restoring file-level backups.

A reference copy may comprise copy(ies) of selected objects from backedup data, typically to help organize data by keeping contextualinformation from multiple sources together, and/or help retain specificdata for a longer period of time, such as for legal hold needs. Areference copy generally maintains data integrity, and when the data isrestored, it may be viewed in the same format as the source data. Insome embodiments, a reference copy is based on a specialized client,individual subclient and associated information management policies(e.g., storage policy, retention policy, etc.) that are administeredwithin system 100.

Archive Operations

Because backup operations generally involve maintaining a version of thecopied primary data 112 and also maintaining backup copies in secondarystorage device(s) 108, they can consume significant storage capacity. Toreduce storage consumption, an archive operation according to certainembodiments creates an archive copy 116 by both copying and removingsource data. Or, seen another way, archive operations can involve movingsome or all of the source data to the archive destination. Thus, datasatisfying criteria for removal (e.g., data of a threshold age or size)may be removed from source storage. The source data may be primary data112 or a secondary copy 116, depending on the situation. As with backupcopies, archive copies can be stored in a format in which the data iscompressed, encrypted, deduplicated, and/or otherwise modified from theformat of the original application or source copy. In addition, archivecopies may be retained for relatively long periods of time (e.g., years)and, in some cases are never deleted. In certain embodiments, archivecopies may be made and kept for extended periods in order to meetcompliance regulations.

Archiving can also serve the purpose of freeing up space in primarystorage device(s) 104 and easing the demand on computational resourceson client computing device 102. Similarly, when a secondary copy 116 isarchived, the archive copy can therefore serve the purpose of freeing upspace in the source secondary storage device(s) 108. Examples of dataarchiving operations are provided in U.S. Pat. No. 7,107,298.

Snapshot Operations

Snapshot operations can provide a relatively lightweight, efficientmechanism for protecting data. From an end-user viewpoint, a snapshotmay be thought of as an “instant” image of primary data 112 at a givenpoint in time and may include state and/or status information relativeto an application 110 that creates/manages primary data 112. In oneembodiment, a snapshot may generally capture the directory structure ofan object in primary data 112 such as a file or volume or other data setat a particular moment in time and may also preserve file attributes andcontents. A snapshot in some cases is created relatively quickly, e.g.,substantially instantly, using a minimum amount of file space, but maystill function as a conventional file system backup.

A “hardware snapshot” (or “hardware-based snapshot”) operation occurswhere a target storage device (e.g., a primary storage device 104 or asecondary storage device 108) performs the snapshot operation in aself-contained fashion, substantially independently, using hardware,firmware and/or software operating on the storage device itself. Forinstance, the storage device may perform snapshot operations generallywithout intervention or oversight from any of the other components ofthe system 100, e.g., a storage array may generate an “array-created”hardware snapshot and may also manage its storage, integrity,versioning, etc. In this manner, hardware snapshots can off-load othercomponents of system 100 from snapshot processing. An array may receivea request from another component to take a snapshot and then proceed toexecute the “hardware snapshot” operations autonomously, preferablyreporting success to the requesting component.

A “software snapshot” (or “software-based snapshot”) operation, on theother hand, occurs where a component in system 100 (e.g., clientcomputing device 102, etc.) implements a software layer that manages thesnapshot operation via interaction with the target storage device. Forinstance, the component executing the snapshot management software layermay derive a set of pointers and/or data that represents the snapshot.The snapshot management software layer may then transmit the same to thetarget storage device, along with appropriate instructions for writingthe snapshot. One example of a software snapshot product is MicrosoftVolume Snapshot Service (VSS), which is part of the Microsoft Windowsoperating system.

Some types of snapshots do not actually create another physical copy ofall the data as it existed at the particular point in time, but maysimply create pointers that map files and directories to specific memorylocations (e.g., to specific disk blocks) where the data resides as itexisted at the particular point in time. For example, a snapshot copymay include a set of pointers derived from the file system or from anapplication. In some other cases, the snapshot may be created at theblock-level, such that creation of the snapshot occurs without awarenessof the file system. Each pointer points to a respective stored datablock, so that collectively, the set of pointers reflect the storagelocation and state of the data object (e.g., file(s) or volume(s) ordata set(s)) at the point in time when the snapshot copy was created.

An initial snapshot may use only a small amount of disk space needed torecord a mapping or other data structure representing or otherwisetracking the blocks that correspond to the current state of the filesystem. Additional disk space is usually required only when files anddirectories change later on. Furthermore, when files change, typicallyonly the pointers which map to blocks are copied, not the blocksthemselves. For example for “copy-on-write” snapshots, when a blockchanges in primary storage, the block is copied to secondary storage orcached in primary storage before the block is overwritten in primarystorage, and the pointer to that block is changed to reflect the newlocation of that block. The snapshot mapping of file system data mayalso be updated to reflect the changed block(s) at that particular pointin time. In some other cases, a snapshot includes a full physical copyof all or substantially all of the data represented by the snapshot.Further examples of snapshot operations are provided in U.S. Pat. No.7,529,782. A snapshot copy in many cases can be made quickly and withoutsignificantly impacting primary computing resources because largeamounts of data need not be copied or moved. In some embodiments, asnapshot may exist as a virtual file system, parallel to the actual filesystem. Users in some cases gain read-only access to the record of filesand directories of the snapshot. By electing to restore primary data 112from a snapshot taken at a given point in time, users may also returnthe current file system to the state of the file system that existedwhen the snapshot was taken.

Replication Operations

Replication is another type of secondary copy operation. Some types ofsecondary copies 116 periodically capture images of primary data 112 atparticular points in time (e.g., backups, archives, and snapshots).However, it can also be useful for recovery purposes to protect primarydata 112 in a more continuous fashion, by replicating primary data 112substantially as changes occur. In some cases, a replication copy can bea mirror copy, for instance, where changes made to primary data 112 aremirrored or substantially immediately copied to another location (e.g.,to secondary storage device(s) 108). By copying each write operation tothe replication copy, two storage systems are kept synchronized orsubstantially synchronized so that they are virtually identical atapproximately the same time. Where entire disk volumes are mirrored,however, mirroring can require significant amount of storage space andutilizes a large amount of processing resources.

According to some embodiments, secondary copy operations are performedon replicated data that represents a recoverable state, or “known goodstate” of a particular application running on the source system. Forinstance, in certain embodiments, known good replication copies may beviewed as copies of primary data 112. This feature allows the system todirectly access, copy, restore, back up, or otherwise manipulate thereplication copies as if they were the “live” primary data 112. This canreduce access time, storage utilization, and impact on sourceapplications 110, among other benefits. Based on known good stateinformation, system 100 can replicate sections of application data thatrepresent a recoverable state rather than rote copying of blocks ofdata. Examples of replication operations (e.g., continuous datareplication) are provided in U.S. Pat. No. 7,617,262.

Deduplication/Single-Instancing Operations

Deduplication or single-instance storage is useful to reduce the amountof non-primary data. For instance, some or all of the above-describedsecondary copy operations can involve deduplication in some fashion. Newdata is read, broken down into data portions of a selected granularity(e.g., sub-file level blocks, files, etc.), compared with correspondingportions that are already in secondary storage, and only new/changedportions are stored. Portions that already exist are represented aspointers to the already-stored data. Thus, a deduplicated secondary copy116 may comprise actual data portions copied from primary data 112 andmay further comprise pointers to already-stored data, which is generallymore storage-efficient than a full copy.

In order to streamline the comparison process, system 100 may calculateand/or store signatures (e.g., hashes or cryptographically unique IDs)corresponding to the individual source data portions and compare thesignatures to already-stored data signatures, instead of comparingentire data portions. In some cases, only a single instance of each dataportion is stored, and deduplication operations may therefore bereferred to interchangeably as “single-instancing” operations. Dependingon the implementation, however, deduplication operations can store morethan one instance of certain data portions, yet still significantlyreduce stored-data redundancy. Depending on the embodiment,deduplication portions such as data blocks can be of fixed or variablelength. Using variable length blocks can enhance deduplication byresponding to changes in the data stream, but can involve more complexprocessing. In some cases, system 100 utilizes a technique fordynamically aligning deduplication blocks based on changing content inthe data stream, as described in U.S. Pat. No. 8,364,652.

System 100 can deduplicate in a variety of manners at a variety oflocations. For instance, in some embodiments, system 100 implements“target-side” deduplication by deduplicating data at the media agent 144after being received from data agent 142. In some such cases, mediaagents 144 are generally configured to manage the deduplication process.For instance, one or more of the media agents 144 maintain acorresponding deduplication database that stores deduplicationinformation (e.g., data block signatures). Examples of such aconfiguration are provided in U.S. Pat. No. 9,020,900. Instead of or incombination with “target-side” deduplication, “source-side” (or“client-side”) deduplication can also be performed, e.g., to reduce theamount of data to be transmitted by data agent 142 to media agent 144.Storage manager 140 may communicate with other components within system100 via network protocols and cloud service provider APIs to facilitatecloud-based deduplication/single instancing, as exemplified in U.S. Pat.No. 8,954,446. Some other deduplication/single instancing techniques aredescribed in U.S. Pat. Pub. No. 2006/0224846 and in U.S. Pat. No.9,098,495.

Information Lifecycle Management and Hierarchical Storage Management

In some embodiments, files and other data over their lifetime move frommore expensive quick-access storage to less expensive slower-accessstorage. Operations associated with moving data through various tiers ofstorage are sometimes referred to as information lifecycle management(ILM) operations.

One type of ILM operation is a hierarchical storage management (HSM)operation, which generally automatically moves data between classes ofstorage devices, such as from high-cost to low-cost storage devices. Forinstance, an HSM operation may involve movement of data from primarystorage devices 104 to secondary storage devices 108, or between tiersof secondary storage devices 108. With each tier, the storage devicesmay be progressively cheaper, have relatively slower access/restoretimes, etc. For example, movement of data between tiers may occur asdata becomes less important over time. In some embodiments, an HSMoperation is similar to archiving in that creating an HSM copy may(though not always) involve deleting some of the source data, e.g.,according to one or more criteria related to the source data. Forexample, an HSM copy may include primary data 112 or a secondary copy116 that exceeds a given size threshold or a given age threshold. Often,and unlike some types of archive copies, HSM data that is removed oraged from the source is replaced by a logical reference pointer or stub.The reference pointer or stub can be stored in the primary storagedevice 104 or other source storage device, such as a secondary storagedevice 108 to replace the deleted source data and to point to orotherwise indicate the new location in (another) secondary storagedevice 108.

For example, files are generally moved between higher and lower coststorage depending on how often the files are accessed. When a userrequests access to HSM data that has been removed or migrated, system100 uses the stub to locate the data and can make recovery of the dataappear transparent, even though the HSM data may be stored at a locationdifferent from other source data. In this manner, the data appears tothe user (e.g., in file system browsing windows and the like) as if itstill resides in the source location (e.g., in a primary storage device104). The stub may include metadata associated with the correspondingdata, so that a file system and/or application can provide someinformation about the data object and/or a limited-functionality version(e.g., a preview) of the data object.

An HSM copy may be stored in a format other than the native applicationformat (e.g., compressed, encrypted, deduplicated, and/or otherwisemodified). In some cases, copies which involve the removal of data fromsource storage and the maintenance of stub or other logical referenceinformation on source storage may be referred to generally as “on-linearchive copies.” On the other hand, copies which involve the removal ofdata from source storage without the maintenance of stub or otherlogical reference information on source storage may be referred to as“off-line archive copies.” Examples of HSM and ILM techniques areprovided in U.S. Pat. No. 7,343,453.

Auxiliary Copy Operations

An auxiliary copy is generally a copy of an existing secondary copy 116.For instance, an initial secondary copy 116 may be derived from primarydata 112 or from data residing in secondary storage subsystem 118,whereas an auxiliary copy is generated from the initial secondary copy116. Auxiliary copies provide additional standby copies of data and mayreside on different secondary storage devices 108 than the initialsecondary copies 116. Thus, auxiliary copies can be used for recoverypurposes if initial secondary copies 116 become unavailable. Exemplaryauxiliary copy techniques are described in further detail in U.S. Pat.No. 8,230,195.

Disaster-Recovery Copy Operations

System 100 may also make and retain disaster recovery copies, often assecondary, high-availability disk copies. System 100 may createsecondary copies and store them at disaster recovery locations usingauxiliary copy or replication operations, such as continuous datareplication technologies. Depending on the particular data protectiongoals, disaster recovery locations can be remote from the clientcomputing devices 102 and primary storage devices 104, remote from someor all of the secondary storage devices 108, or both.

Data Manipulation, Including Encryption and Compression

Data manipulation and processing may include encryption and compressionas well as integrity marking and checking, formatting for transmission,formatting for storage, etc. Data may be manipulated “client-side” bydata agent 142 as well as “target-side” by media agent 144 in the courseof creating secondary copy 116, or conversely in the course of restoringdata from secondary to primary.

Encryption Operations

System 100 in some cases is configured to process data (e.g., files orother data objects, primary data 112, secondary copies 116, etc.),according to an appropriate encryption algorithm (e.g., Blowfish,Advanced Encryption Standard (AES), Triple Data Encryption Standard(3-DES), etc.) to limit access and provide data security. System 100 insome cases encrypts the data at the client level, such that clientcomputing devices 102 (e.g., data agents 142) encrypt the data prior totransferring it to other components, e.g., before sending the data tomedia agents 144 during a secondary copy operation. In such cases,client computing device 102 may maintain or have access to an encryptionkey or passphrase for decrypting the data upon restore. Encryption canalso occur when media agent 144 creates auxiliary copies or archivecopies. Encryption may be applied in creating a secondary copy 116 of apreviously unencrypted secondary copy 116, without limitation. Infurther embodiments, secondary storage devices 108 can implementbuilt-in, high performance hardware-based encryption.

Compression Operations

Similar to encryption, system 100 may also or alternatively compressdata in the course of generating a secondary copy 116. Compressionencodes information such that fewer bits are needed to represent theinformation as compared to the original representation. Compressiontechniques are well known in the art. Compression operations may applyone or more data compression algorithms. Compression may be applied increating a secondary copy 116 of a previously uncompressed secondarycopy, e.g., when making archive copies or disaster recovery copies. Theuse of compression may result in metadata that specifies the nature ofthe compression, so that data may be uncompressed on restore ifappropriate.

Data Analysis, Reporting, and Management Operations

Data analysis, reporting, and management operations can differ from datamovement operations in that they do not necessarily involve copying,migration or other transfer of data between different locations in thesystem. For instance, data analysis operations may involve processing(e.g., offline processing) or modification of already stored primarydata 112 and/or secondary copies 116. However, in some embodiments dataanalysis operations are performed in conjunction with data movementoperations. Some data analysis operations include content indexingoperations and classification operations which can be useful inleveraging data under management to enhance search and other features.

Classification Operations/Content Indexing

In some embodiments, information management system 100 analyzes andindexes characteristics, content, and metadata associated with primarydata 112 (“online content indexing”) and/or secondary copies 116(“off-line content indexing”). Content indexing can identify files orother data objects based on content (e.g., user-defined keywords orphrases, other keywords/phrases that are not defined by a user, etc.),and/or metadata (e.g., email metadata such as “to,” “from,” “cc,” “bcc,”attachment name, received time, etc.). Content indexes may be searched,and search results may be restored.

System 100 generally organizes and catalogues the results into a contentindex, which may be stored within media agent database 152, for example.The content index can also include the storage locations of or pointerreferences to indexed data in primary data 112 and/or secondary copies116. Results may also be stored elsewhere in system 100 (e.g., inprimary storage device 104 or in secondary storage device 108). Suchcontent index data provides storage manager 140 or other components withan efficient mechanism for locating primary data 112 and/or secondarycopies 116 of data objects that match particular criteria, thus greatlyincreasing the search speed capability of system 100. For instance,search criteria can be specified by a user through user interface 158 ofstorage manager 140. Moreover, when system 100 analyzes data and/ormetadata in secondary copies 116 to create an “off-line content index,”this operation has no significant impact on the performance of clientcomputing devices 102 and thus does not take a toll on the productionenvironment. Examples of content indexing techniques are provided inU.S. Pat. No. 8,170,995.

One or more components, such as a content index engine, can beconfigured to scan data and/or associated metadata for classificationpurposes to populate a database (or other data structure) ofinformation, which can be referred to as a “data classificationdatabase” or a “metabase.” Depending on the embodiment, the dataclassification database(s) can be organized in a variety of differentways, including centralization, logical sub-divisions, and/or physicalsub-divisions. For instance, one or more data classification databasesmay be associated with different subsystems or tiers within system 100.As an example, there may be a first metabase associated with primarystorage subsystem 117 and a second metabase associated with secondarystorage subsystem 118. In other cases, metabase(s) may be associatedwith individual components, e.g., client computing devices 102 and/ormedia agents 144. In some embodiments, a data classification databasemay reside as one or more data structures within management database146, may be otherwise associated with storage manager 140, and/or mayreside as a separate component. In some cases, metabase(s) may beincluded in separate database(s) and/or on separate storage device(s)from primary data 112 and/or secondary copies 116, such that operationsrelated to the metabase(s) do not significantly impact performance onother components of system 100. In other cases, metabase(s) may bestored along with primary data 112 and/or secondary copies 116. Files orother data objects can be associated with identifiers (e.g., tagentries, etc.) to facilitate searches of stored data objects. Among anumber of other benefits, the metabase can also allow efficient,automatic identification of files or other data objects to associatewith secondary copy or other information management operations. Forinstance, a metabase can dramatically improve the speed with whichsystem 100 can search through and identify data as compared to otherapproaches that involve scanning an entire file system. Examples ofmetabases and data classification operations are provided in U.S. Pat.Nos. 7,734,669 and 7,747,579.

Management and Reporting Operations

Certain embodiments leverage the integrated ubiquitous nature of system100 to provide useful system-wide management and reporting. Operationsmanagement can generally include monitoring and managing the health andperformance of system 100 by, without limitation, performing errortracking, generating granular storage/performance metrics (e.g., jobsuccess/failure information, deduplication efficiency, etc.), generatingstorage modeling and costing information, and the like. As an example,storage manager 140 or another component in system 100 may analyzetraffic patterns and suggest and/or automatically route data to minimizecongestion. In some embodiments, the system can generate predictionsrelating to storage operations or storage operation information. Suchpredictions, which may be based on a trending analysis, may predictvarious network operations or resource usage, such as network trafficlevels, storage media use, use of bandwidth of communication links, useof media agent components, etc. Further examples of traffic analysis,trend analysis, prediction generation, and the like are described inU.S. Pat. No. 7,343,453.

In some configurations having a hierarchy of storage operation cells, amaster storage manager 140 may track the status of subordinate cells,such as the status of jobs, system components, system resources, andother items, by communicating with storage managers 140 (or othercomponents) in the respective storage operation cells. Moreover, themaster storage manager 140 may also track status by receiving periodicstatus updates from the storage managers 140 (or other components) inthe respective cells regarding jobs, system components, systemresources, and other items. In some embodiments, a master storagemanager 140 may store status information and other information regardingits associated storage operation cells and other system information inits management database 146 and/or index 150 (or in another location).The master storage manager 140 or other component may also determinewhether certain storage-related or other criteria are satisfied, and mayperform an action or trigger event (e.g., data migration) in response tothe criteria being satisfied, such as where a storage threshold is metfor a particular volume, or where inadequate protection exists forcertain data. For instance, data from one or more storage operationcells is used to dynamically and automatically mitigate recognizedrisks, and/or to advise users of risks or suggest actions to mitigatethese risks. For example, an information management policy may specifycertain requirements (e.g., that a storage device should maintain acertain amount of free space, that secondary copies should occur at aparticular interval, that data should be aged and migrated to otherstorage after a particular period, that data on a secondary volumeshould always have a certain level of availability and be restorablewithin a given time period, that data on a secondary volume may bemirrored or otherwise migrated to a specified number of other volumes,etc.). If a risk condition or other criterion is triggered, the systemmay notify the user of these conditions and may suggest (orautomatically implement) a mitigation action to address the risk. Forexample, the system may indicate that data from a primary copy 112should be migrated to a secondary storage device 108 to free up space onprimary storage device 104. Examples of the use of risk factors andother triggering criteria are described in U.S. Pat. No. 7,343,453.

In some embodiments, system 100 may also determine whether a metric orother indication satisfies particular storage criteria sufficient toperform an action. For example, a storage policy or other definitionmight indicate that a storage manager 140 should initiate a particularaction if a storage metric or other indication drops below or otherwisefails to satisfy specified criteria such as a threshold of dataprotection. In some embodiments, risk factors may be quantified intocertain measurable service or risk levels. For example, certainapplications and associated data may be considered to be more importantrelative to other data and services. Financial compliance data, forexample, may be of greater importance than marketing materials, etc.Network administrators may assign priority values or “weights” tocertain data and/or applications corresponding to the relativeimportance. The level of compliance of secondary copy operationsspecified for these applications may also be assigned a certain value.Thus, the health, impact, and overall importance of a service may bedetermined, such as by measuring the compliance value and calculatingthe product of the priority value and the compliance value to determinethe “service level” and comparing it to certain operational thresholdsto determine whether it is acceptable. Further examples of the servicelevel determination are provided in U.S. Pat. No. 7,343,453.

System 100 may additionally calculate data costing and data availabilityassociated with information management operation cells. For instance,data received from a cell may be used in conjunction withhardware-related information and other information about system elementsto determine the cost of storage and/or the availability of particulardata. Exemplary information generated could include how fast aparticular department is using up available storage space, how long datawould take to recover over a particular pathway from a particularsecondary storage device, costs over time, etc. Moreover, in someembodiments, such information may be used to determine or predict theoverall cost associated with the storage of certain information. Thecost associated with hosting a certain application may be based, atleast in part, on the type of media on which the data resides, forexample. Storage devices may be assigned to a particular costcategories, for example. Further examples of costing techniques aredescribed in U.S. Pat. No. 7,343,453.

Any of the above types of information (e.g., information related totrending, predictions, job, cell or component status, risk, servicelevel, costing, etc.) can generally be provided to users via userinterface 158 in a single integrated view or console (not shown). Reporttypes may include: scheduling, event management, media management anddata aging. Available reports may also include backup history, dataaging history, auxiliary copy history, job history, library and drive,media in library, restore history, and storage policy, etc., withoutlimitation. Such reports may be specified and created at a certain pointin time as a system analysis, forecasting, or provisioning tool.Integrated reports may also be generated that illustrate storage andperformance metrics, risks and storage costing information. Moreover,users may create their own reports based on specific needs. Userinterface 158 can include an option to graphically depict the variouscomponents in the system using appropriate icons. As one example, userinterface 158 may provide a graphical depiction of primary storagedevices 104, secondary storage devices 108, data agents 142 and/or mediaagents 144, and their relationship to one another in system 100.

In general, the operations management functionality of system 100 canfacilitate planning and decision-making. For example, in someembodiments, a user may view the status of some or all jobs as well asthe status of each component of information management system 100. Usersmay then plan and make decisions based on this data. For instance, auser may view high-level information regarding secondary copy operationsfor system 100, such as job status, component status, resource status(e.g., communication pathways, etc.), and other information. The usermay also drill down or use other means to obtain more detailedinformation regarding a particular component, job, or the like. Furtherexamples are provided in U.S. Pat. No. 7,343,453.

System 100 can also be configured to perform system-wide e-discoveryoperations in some embodiments. In general, e-discovery operationsprovide a unified collection and search capability for data in thesystem, such as data stored in secondary storage devices 108 (e.g.,backups, archives, or other secondary copies 116). For example, system100 may construct and maintain a virtual repository for data stored insystem 100 that is integrated across source applications 110, differentstorage device types, etc. According to some embodiments, e-discoveryutilizes other techniques described herein, such as data classificationand/or content indexing.

Information Management Policies

An information management policy 148 can include a data structure orother information source that specifies a set of parameters (e.g.,criteria and rules) associated with secondary copy and/or otherinformation management operations.

One type of information management policy 148 is a “storage policy.”According to certain embodiments, a storage policy generally comprises adata structure or other information source that defines (or includesinformation sufficient to determine) a set of preferences or othercriteria for performing information management operations. Storagepolicies can include one or more of the following: (1) what data will beassociated with the storage policy, e.g., subclient; (2) a destinationto which the data will be stored; (3) datapath information specifyinghow the data will be communicated to the destination; (4) the type ofsecondary copy operation to be performed; and (5) retention informationspecifying how long the data will be retained at the destination (see,e.g., FIG. 1E). Data associated with a storage policy can be logicallyorganized into subclients, which may represent primary data 112 and/orsecondary copies 116. A subclient may represent static or dynamicassociations of portions of a data volume. Subclients may representmutually exclusive portions. Thus, in certain embodiments, a portion ofdata may be given a label and the association is stored as a staticentity in an index, database or other storage location. Subclients mayalso be used as an effective administrative scheme of organizing dataaccording to data type, department within the enterprise, storagepreferences, or the like. Depending on the configuration, subclients cancorrespond to files, folders, virtual machines, databases, etc. In oneexemplary scenario, an administrator may find it preferable to separatee-mail data from financial data using two different subclients.

A storage policy can define where data is stored by specifying a targetor destination storage device (or group of storage devices). Forinstance, where the secondary storage device 108 includes a group ofdisk libraries, the storage policy may specify a particular disk libraryfor storing the subclients associated with the policy. As anotherexample, where the secondary storage devices 108 include one or moretape libraries, the storage policy may specify a particular tape libraryfor storing the subclients associated with the storage policy, and mayalso specify a drive pool and a tape pool defining a group of tapedrives and a group of tapes, respectively, for use in storing thesubclient data. While information in the storage policy can bestatically assigned in some cases, some or all of the information in thestorage policy can also be dynamically determined based on criteria setforth in the storage policy. For instance, based on such criteria, aparticular destination storage device(s) or other parameter of thestorage policy may be determined based on characteristics associatedwith the data involved in a particular secondary copy operation, deviceavailability (e.g., availability of a secondary storage device 108 or amedia agent 144), network status and conditions (e.g., identifiedbottlenecks), user credentials, and the like.

Datapath information can also be included in the storage policy. Forinstance, the storage policy may specify network pathways and componentsto utilize when moving the data to the destination storage device(s). Insome embodiments, the storage policy specifies one or more media agents144 for conveying data associated with the storage policy between thesource and destination. A storage policy can also specify the type(s) ofassociated operations, such as backup, archive, snapshot, auxiliarycopy, or the like. Furthermore, retention parameters can specify howlong the resulting secondary copies 116 will be kept (e.g., a number ofdays, months, years, etc.), perhaps depending on organizational needsand/or compliance criteria.

When adding a new client computing device 102, administrators canmanually configure information management policies 148 and/or othersettings, e.g., via user interface 158. However, this can be an involvedprocess resulting in delays, and it may be desirable to begin dataprotection operations quickly, without awaiting human intervention.Thus, in some embodiments, system 100 automatically applies a defaultconfiguration to client computing device 102. As one example, when oneor more data agent(s) 142 are installed on a client computing device102, the installation script may register the client computing device102 with storage manager 140, which in turn applies the defaultconfiguration to the new client computing device 102. In this manner,data protection operations can begin substantially immediately. Thedefault configuration can include a default storage policy, for example,and can specify any appropriate information sufficient to begin dataprotection operations. This can include a type of data protectionoperation, scheduling information, a target secondary storage device108, data path information (e.g., a particular media agent 144), and thelike.

Another type of information management policy 148 is a “schedulingpolicy,” which specifies when and how often to perform operations.Scheduling parameters may specify with what frequency (e.g., hourly,weekly, daily, event-based, etc.) or under what triggering conditionssecondary copy or other information management operations are to takeplace. Scheduling policies in some cases are associated with particularcomponents, such as a subclient, client computing device 102, and thelike.

Another type of information management policy 148 is an “audit policy”(or “security policy”), which comprises preferences, rules and/orcriteria that protect sensitive data in system 100. For example, anaudit policy may define “sensitive objects” which are files or dataobjects that contain particular keywords (e.g., “confidential,” or“privileged”) and/or are associated with particular keywords (e.g., inmetadata) or particular flags (e.g., in metadata identifying a documentor email as personal, confidential, etc.). An audit policy may furtherspecify rules for handling sensitive objects. As an example, an auditpolicy may require that a reviewer approve the transfer of any sensitiveobjects to a cloud storage site, and that if approval is denied for aparticular sensitive object, the sensitive object should be transferredto a local primary storage device 104 instead. To facilitate thisapproval, the audit policy may further specify how a secondary storagecomputing device 106 or other system component should notify a reviewerthat a sensitive object is slated for transfer.

Another type of information management policy 148 is a “provisioningpolicy,” which can include preferences, priorities, rules, and/orcriteria that specify how client computing devices 102 (or groupsthereof) may utilize system resources, such as available storage oncloud storage and/or network bandwidth. A provisioning policy specifies,for example, data quotas for particular client computing devices 102(e.g., a number of gigabytes that can be stored monthly, quarterly orannually). Storage manager 140 or other components may enforce theprovisioning policy. For instance, media agents 144 may enforce thepolicy when transferring data to secondary storage devices 108. If aclient computing device 102 exceeds a quota, a budget for the clientcomputing device 102 (or associated department) may be adjustedaccordingly or an alert may trigger.

While the above types of information management policies 148 aredescribed as separate policies, one or more of these can be generallycombined into a single information management policy 148. For instance,a storage policy may also include or otherwise be associated with one ormore scheduling, audit, or provisioning policies or operationalparameters thereof. Moreover, while storage policies are typicallyassociated with moving and storing data, other policies may beassociated with other types of information management operations. Thefollowing is a non-exhaustive list of items that information managementpolicies 148 may specify:

-   -   schedules or other timing information, e.g., specifying when        and/or how often to perform information management operations;    -   the type of secondary copy 116 and/or copy format (e.g.,        snapshot, backup, archive, HSM, etc.);    -   a location or a class or quality of storage for storing        secondary copies 116 (e.g., one or more particular secondary        storage devices 108);    -   preferences regarding whether and how to encrypt, compress,        deduplicate, or otherwise modify or transform secondary copies        116;    -   which system components and/or network pathways (e.g., preferred        media agents 144) should be used to perform secondary storage        operations;    -   resource allocation among different computing devices or other        system components used in performing information management        operations (e.g., bandwidth allocation, available storage        capacity, etc.);    -   whether and how to synchronize or otherwise distribute files or        other data objects across multiple computing devices or hosted        services; and    -   retention information specifying the length of time primary data        112 and/or secondary copies 116 should be retained, e.g., in a        particular class or tier of storage devices, or within the        system 100.

Information management policies 148 can additionally specify or dependon historical or current criteria that may be used to determine whichrules to apply to a particular data object, system component, orinformation management operation, such as:

-   -   frequency with which primary data 112 or a secondary copy 116 of        a data object or metadata has been or is predicted to be used,        accessed, or modified;    -   time-related factors (e.g., aging information such as time since        the creation or modification of a data object);    -   deduplication information (e.g., hashes, data blocks,        deduplication block size, deduplication efficiency or other        metrics);    -   an estimated or historic usage or cost associated with different        components (e.g., with secondary storage devices 108);    -   the identity of users, applications 110, client computing        devices 102 and/or other computing devices that created,        accessed, modified, or otherwise utilized primary data 112 or        secondary copies 116;    -   a relative sensitivity (e.g., confidentiality, importance) of a        data object, e.g., as determined by its content and/or metadata;    -   the current or historical storage capacity of various storage        devices;    -   the current or historical network capacity of network pathways        connecting various components within the storage operation cell;    -   access control lists or other security information; and    -   the content of a particular data object (e.g., its textual        content) or of metadata associated with the data object.

Exemplary Storage Policy and Secondary Copy Operations

FIG. 1E includes a data flow diagram depicting performance of secondarycopy operations by an embodiment of information management system 100,according to an exemplary storage policy 148A. System 100 includes astorage manager 140, a client computing device 102 having a file systemdata agent 142A and an email data agent 142B operating thereon, aprimary storage device 104, two media agents 144A, 144B, and twosecondary storage devices 108: a disk library 108A and a tape library108B. As shown, primary storage device 104 includes primary data 112A,which is associated with a logical grouping of data associated with afile system (“file system subclient”), and primary data 112B, which is alogical grouping of data associated with email (“email subclient”). Thetechniques described with respect to FIG. 1E can be utilized inconjunction with data that is otherwise organized as well.

As indicated by the dashed box, the second media agent 144B and tapelibrary 108B are “off-site,” and may be remotely located from the othercomponents in system 100 (e.g., in a different city, office building,etc.). Indeed, “off-site” may refer to a magnetic tape located in remotestorage, which must be manually retrieved and loaded into a tape driveto be read. In this manner, information stored on the tape library 108Bmay provide protection in the event of a disaster or other failure atthe main site(s) where data is stored.

The file system subclient 112A in certain embodiments generallycomprises information generated by the file system and/or operatingsystem of client computing device 102, and can include, for example,file system data (e.g., regular files, file tables, mount points, etc.),operating system data (e.g., registries, event logs, etc.), and thelike. The e-mail subclient 112B can include data generated by an e-mailapplication operating on client computing device 102, e.g., mailboxinformation, folder information, emails, attachments, associateddatabase information, and the like. As described above, the subclientscan be logical containers, and the data included in the correspondingprimary data 112A and 112B may or may not be stored contiguously.

The exemplary storage policy 148A includes backup copy preferences orrule set 160, disaster recovery copy preferences or rule set 162, andcompliance copy preferences or rule set 164. Backup copy rule set 160specifies that it is associated with file system subclient 166 and emailsubclient 168. Each of subclients 166 and 168 are associated with theparticular client computing device 102. Backup copy rule set 160 furtherspecifies that the backup operation will be written to disk library 108Aand designates a particular media agent 144A to convey the data to disklibrary 108A. Finally, backup copy rule set 160 specifies that backupcopies created according to rule set 160 are scheduled to be generatedhourly and are to be retained for 30 days. In some other embodiments,scheduling information is not included in storage policy 148A and isinstead specified by a separate scheduling policy.

Disaster recovery copy rule set 162 is associated with the same twosubclients 166 and 168. However, disaster recovery copy rule set 162 isassociated with tape library 108B, unlike backup copy rule set 160.Moreover, disaster recovery copy rule set 162 specifies that a differentmedia agent, namely 144B, will convey data to tape library 108B.Disaster recovery copies created according to rule set 162 will beretained for 60 days and will be generated daily. Disaster recoverycopies generated according to disaster recovery copy rule set 162 canprovide protection in the event of a disaster or other catastrophic dataloss that would affect the backup copy 116A maintained on disk library108A.

Compliance copy rule set 164 is only associated with the email subclient168, and not the file system subclient 166. Compliance copies generatedaccording to compliance copy rule set 164 will therefore not includeprimary data 112A from the file system subclient 166. For instance, theorganization may be under an obligation to store and maintain copies ofemail data for a particular period of time (e.g., 10 years) to complywith state or federal regulations, while similar regulations do notapply to file system data. Compliance copy rule set 164 is associatedwith the same tape library 108B and media agent 144B as disasterrecovery copy rule set 162, although a different storage device or mediaagent could be used in other embodiments. Finally, compliance copy ruleset 164 specifies that the copies it governs will be generated quarterlyand retained for 10 years.

Secondary Copy Jobs

A logical grouping of secondary copy operations governed by a rule setand being initiated at a point in time may be referred to as a“secondary copy job” (and sometimes may be called a “backup job,” eventhough it is not necessarily limited to creating only backup copies).Secondary copy jobs may be initiated on demand as well. Steps 1-9 belowillustrate three secondary copy jobs based on storage policy 148A.

Referring to FIG. 1E, at step 1, storage manager 140 initiates a backupjob according to the backup copy rule set 160, which logically comprisesall the secondary copy operations necessary to effectuate rules 160 instorage policy 148A every hour, including steps 1-4 occurring hourly.For instance, a scheduling service running on storage manager 140accesses backup copy rule set 160 or a separate scheduling policyassociated with client computing device 102 and initiates a backup jobon an hourly basis. Thus, at the scheduled time, storage manager 140sends instructions to client computing device 102 (i.e., to both dataagent 142A and data agent 142B) to begin the backup job.

At step 2, file system data agent 142A and email data agent 142B onclient computing device 102 respond to instructions from storage manager140 by accessing and processing the respective subclient primary data112A and 112B involved in the backup copy operation, which can be foundin primary storage device 104. Because the secondary copy operation is abackup copy operation, the data agent(s) 142A, 142B may format the datainto a backup format or otherwise process the data suitable for a backupcopy.

At step 3, client computing device 102 communicates the processed filesystem data (e.g., using file system data agent 142A) and the processedemail data (e.g., using email data agent 142B) to the first media agent144A according to backup copy rule set 160, as directed by storagemanager 140. Storage manager 140 may further keep a record in managementdatabase 146 of the association between media agent 144A and one or moreof: client computing device 102, file system subclient 112A, file systemdata agent 142A, email subclient 112B, email data agent 142B, and/orbackup copy 116A.

The target media agent 144A receives the data-agent-processed data fromclient computing device 102, and at step 4 generates and conveys backupcopy 116A to disk library 108A to be stored as backup copy 116A, againat the direction of storage manager 140 and according to backup copyrule set 160. Media agent 144A can also update its index 153 to includedata and/or metadata related to backup copy 116A, such as informationindicating where the backup copy 116A resides on disk library 108A,where the email copy resides, where the file system copy resides, dataand metadata for cache retrieval, etc. Storage manager 140 may similarlyupdate its index 150 to include information relating to the secondarycopy operation, such as information relating to the type of operation, aphysical location associated with one or more copies created by theoperation, the time the operation was performed, status informationrelating to the operation, the components involved in the operation, andthe like. In some cases, storage manager 140 may update its index 150 toinclude some or all of the information stored in index 153 of mediaagent 144A. At this point, the backup job may be considered complete.After the 30-day retention period expires, storage manager 140 instructsmedia agent 144A to delete backup copy 116A from disk library 108A andindexes 150 and/or 153 are updated accordingly.

At step 5, storage manager 140 initiates another backup job for adisaster recovery copy according to the disaster recovery rule set 162.Illustratively this includes steps 5-7 occurring daily for creatingdisaster recovery copy 116B. Illustratively, and by way of illustratingthe scalable aspects and off-loading principles embedded in system 100,disaster recovery copy 116B is based on backup copy 116A and not onprimary data 112A and 112B.

At step 6, illustratively based on instructions received from storagemanager 140 at step 5, the specified media agent 1446 retrieves the mostrecent backup copy 116A from disk library 108A.

At step 7, again at the direction of storage manager 140 and asspecified in disaster recovery copy rule set 162, media agent 144B usesthe retrieved data to create a disaster recovery copy 116B and store itto tape library 108B. In some cases, disaster recovery copy 116B is adirect, mirror copy of backup copy 116A, and remains in the backupformat. In other embodiments, disaster recovery copy 116B may be furthercompressed or encrypted, or may be generated in some other manner, suchas by using primary data 112A and 112B from primary storage device 104as sources. The disaster recovery copy operation is initiated once a dayand disaster recovery copies 116B are deleted after 60 days; indexes 153and/or 150 are updated accordingly when/after each informationmanagement operation is executed and/or completed. The present backupjob may be considered completed.

At step 8, storage manager 140 initiates another backup job according tocompliance rule set 164, which performs steps 8-9 quarterly to createcompliance copy 116C. For instance, storage manager 140 instructs mediaagent 144B to create compliance copy 116C on tape library 108B, asspecified in the compliance copy rule set 164.

At step 9 in the example, compliance copy 116C is generated usingdisaster recovery copy 116B as the source. This is efficient, becausedisaster recovery copy resides on the same secondary storage device andthus no network resources are required to move the data. In otherembodiments, compliance copy 116C is instead generated using primarydata 112B corresponding to the email subclient or using backup copy 116Afrom disk library 108A as source data. As specified in the illustratedexample, compliance copies 116C are created quarterly, and are deletedafter ten years, and indexes 153 and/or 150 are kept up-to-dateaccordingly.

Exemplary Applications of Storage Policies—Information GovernancePolicies and Classification

Again referring to FIG. 1E, storage manager 140 may permit a user tospecify aspects of storage policy 148A. For example, the storage policycan be modified to include information governance policies to define howdata should be managed in order to comply with a certain regulation orbusiness objective. The various policies may be stored, for example, inmanagement database 146. An information governance policy may align withone or more compliance tasks that are imposed by regulations or businessrequirements. Examples of information governance policies might includea Sarbanes-Oxley policy, a HIPAA policy, an electronic discovery(e-discovery) policy, and so on.

Information governance policies allow administrators to obtain differentperspectives on an organization's online and offline data, without theneed for a dedicated data silo created solely for each differentviewpoint. As described previously, the data storage systems hereinbuild an index that reflects the contents of a distributed data set thatspans numerous clients and storage devices, including both primary dataand secondary copies, and online and offline copies. An organization mayapply multiple information governance policies in a top-down manner overthat unified data set and indexing schema in order to view andmanipulate the data set through different lenses, each of which isadapted to a particular compliance or business goal. Thus, for example,by applying an e-discovery policy and a Sarbanes-Oxley policy, twodifferent groups of users in an organization can conduct two verydifferent analyses of the same underlying physical set of data/copies,which may be distributed throughout the information management system.

An information governance policy may comprise a classification policy,which defines a taxonomy of classification terms or tags relevant to acompliance task and/or business objective. A classification policy mayalso associate a defined tag with a classification rule. Aclassification rule defines a particular combination of criteria, suchas users who have created, accessed or modified a document or dataobject; file or application types; content or metadata keywords; clientsor storage locations; dates of data creation and/or access; reviewstatus or other status within a workflow (e.g., reviewed orun-reviewed); modification times or types of modifications; and/or anyother data attributes in any combination, without limitation. Aclassification rule may also be defined using other classification tagsin the taxonomy. The various criteria used to define a classificationrule may be combined in any suitable fashion, for example, via Booleanoperators, to define a complex classification rule. As an example, ane-discovery classification policy might define a classification tag“privileged” that is associated with documents or data objects that (1)were created or modified by legal department staff, or (2) were sent toor received from outside counsel via email, or (3) contain one of thefollowing keywords: “privileged” or “attorney” or “counsel,” or otherlike terms. Accordingly, all these documents or data objects will beclassified as “privileged.”

One specific type of classification tag, which may be added to an indexat the time of indexing, is an “entity tag.” An entity tag may be, forexample, any content that matches a defined data mask format. Examplesof entity tags might include, e.g., social security numbers (e.g., anynumerical content matching the formatting mask XXX-XX-XXXX), credit cardnumbers (e.g., content having a 13-16 digit string of numbers), SKUnumbers, product numbers, etc. A user may define a classification policyby indicating criteria, parameters or descriptors of the policy via agraphical user interface, such as a form or page with fields to befilled in, pull-down menus or entries allowing one or more of severaloptions to be selected, buttons, sliders, hypertext links or other knownuser interface tools for receiving user input, etc. For example, a usermay define certain entity tags, such as a particular product number orproject ID. In some implementations, the classification policy can beimplemented using cloud-based techniques. For example, the storagedevices may be cloud storage devices, and the storage manager 140 mayexecute cloud service provider API over a network to classify datastored on cloud storage devices.

Restore Operations from Secondary Copies

While not shown in FIG. 1E, at some later point in time, a restoreoperation can be initiated involving one or more of secondary copies116A, 116B, and 116C. A restore operation logically takes a selectedsecondary copy 116, reverses the effects of the secondary copy operationthat created it, and stores the restored data to primary storage where aclient computing device 102 may properly access it as primary data. Amedia agent 144 and an appropriate data agent 142 (e.g., executing onthe client computing device 102) perform the tasks needed to complete arestore operation. For example, data that was encrypted, compressed,and/or deduplicated in the creation of secondary copy 116 will becorrespondingly rehydrated (reversing deduplication), uncompressed, andunencrypted into a format appropriate to primary data. Metadata storedwithin or associated with the secondary copy 116 may be used during therestore operation. In general, restored data should be indistinguishablefrom other primary data 112. Preferably, the restored data has fullyregained the native format that may make it immediately usable byapplication 110.

As one example, a user may manually initiate a restore of backup copy116A, e.g., by interacting with user interface 158 of storage manager140 or with a web-based console with access to system 100. Storagemanager 140 may accesses data in its index 150 and/or managementdatabase 146 (and/or the respective storage policy 148A) associated withthe selected backup copy 116A to identify the appropriate media agent144A and/or secondary storage device 108A where the secondary copyresides. The user may be presented with a representation (e.g., stub,thumbnail, listing, etc.) and metadata about the selected secondarycopy, in order to determine whether this is the appropriate copy to berestored, e.g., date that the original primary data was created. Storagemanager 140 will then instruct media agent 144A and an appropriate dataagent 142 on the target client computing device 102 to restore secondarycopy 116A to primary storage device 104. A media agent may be selectedfor use in the restore operation based on a load balancing algorithm, anavailability based algorithm, or other criteria. The selected mediaagent, e.g., 144A, retrieves secondary copy 116A from disk library 108A.For instance, media agent 144A may access its index 153 to identify alocation of backup copy 116A on disk library 108A, or may accesslocation information residing on disk library 108A itself.

In some cases, a backup copy 116A that was recently created or accessed,may be cached to speed up the restore operation. In such a case, mediaagent 144A accesses a cached version of backup copy 116A residing inindex 153, without having to access disk library 108A for some or all ofthe data. Once it has retrieved backup copy 116A, the media agent 144Acommunicates the data to the requesting client computing device 102.Upon receipt, file system data agent 142A and email data agent 142B mayunpack (e.g., restore from a backup format to the native applicationformat) the data in backup copy 116A and restore the unpackaged data toprimary storage device 104. In general, secondary copies 116 may berestored to the same volume or folder in primary storage device 104 fromwhich the secondary copy was derived; to another storage location orclient computing device 102; to shared storage, etc. In some cases, thedata may be restored so that it may be used by an application 110 of adifferent version/vintage from the application that created the originalprimary data 112.

Exemplary Secondary Copy Formatting

The formatting and structure of secondary copies 116 can vary dependingon the embodiment. In some cases, secondary copies 116 are formatted asa series of logical data units or “chunks” (e.g., 512 MB, 1 GB, 2 GB, 4GB, or 8 GB chunks). This can facilitate efficient communication andwriting to secondary storage devices 108, e.g., according to resourceavailability. For example, a single secondary copy 116 may be written ona chunk-by-chunk basis to one or more secondary storage devices 108. Insome cases, users can select different chunk sizes, e.g., to improvethroughput to tape storage devices. Generally, each chunk can include aheader and a payload. The payload can include files (or other dataunits) or subsets thereof included in the chunk, whereas the chunkheader generally includes metadata relating to the chunk, some or all ofwhich may be derived from the payload. For example, during a secondarycopy operation, media agent 144, storage manager 140, or other componentmay divide files into chunks and generate headers for each chunk byprocessing the files. Headers can include a variety of information suchas file and/or volume identifier(s), offset(s), and/or other informationassociated with the payload data items, a chunk sequence number, etc.Importantly, in addition to being stored with secondary copy 116 onsecondary storage device 108, chunk headers can also be stored to index153 of the associated media agent(s) 144 and/or to index 150 associatedwith storage manager 140. This can be useful for providing fasterprocessing of secondary copies 116 during browsing, restores, or otheroperations. In some cases, once a chunk is successfully transferred to asecondary storage device 108, the secondary storage device 108 returnsan indication of receipt, e.g., to media agent 144 and/or storagemanager 140, which may update their respective indexes 153, 150accordingly. During restore, chunks may be processed (e.g., by mediaagent 144) according to the information in the chunk header toreassemble the files.

Data can also be communicated within system 100 in data channels thatconnect client computing devices 102 to secondary storage devices 108.These data channels can be referred to as “data streams,” and multipledata streams can be employed to parallelize an information managementoperation, improving data transfer rate, among other advantages. Exampledata formatting techniques including techniques involving datastreaming, chunking, and the use of other data structures in creatingsecondary copies are described in U.S. Pat. Nos. 7,315,923, 8,156,086,and 8,578,120.

FIGS. 1F and 1G are diagrams of example data streams 170 and 171,respectively, which may be employed for performing informationmanagement operations. Referring to FIG. 1F, data agent 142 forms datastream 170 from source data associated with a client computing device102 (e.g., primary data 112). Data stream 170 is composed of multiplepairs of stream header 172 and stream data (or stream payload) 174. Datastreams 170 and 171 shown in the illustrated example are for asingle-instanced storage operation, and a stream payload 174 thereforemay include both single-instance (SI) data and/or non-SI data. A streamheader 172 includes metadata about the stream payload 174. This metadatamay include, for example, a length of the stream payload 174, anindication of whether the stream payload 174 is encrypted, an indicationof whether the stream payload 174 is compressed, an archive fileidentifier (ID), an indication of whether the stream payload 174 issingle instanceable, and an indication of whether the stream payload 174is a start of a block of data.

Referring to FIG. 1G, data stream 171 has the stream header 172 andstream payload 174 aligned into multiple data blocks. In this example,the data blocks are of size 64 KB. The first two stream header 172 andstream payload 174 pairs comprise a first data block of size 64 KB. Thefirst stream header 172 indicates that the length of the succeedingstream payload 174 is 63 KB and that it is the start of a data block.The next stream header 172 indicates that the succeeding stream payload174 has a length of 1 KB and that it is not the start of a new datablock. Immediately following stream payload 174 is a pair comprising anidentifier header 176 and identifier data 178. The identifier header 176includes an indication that the succeeding identifier data 178 includesthe identifier for the immediately previous data block. The identifierdata 178 includes the identifier that the data agent 142 generated forthe data block. The data stream 171 also includes other stream header172 and stream payload 174 pairs, which may be for SI data and/or non-SIdata.

FIG. 1H is a diagram illustrating data structures 180 that may be usedto store blocks of SI data and non-SI data on a storage device (e.g.,secondary storage device 108). According to certain embodiments, datastructures 180 do not form part of a native file system of the storagedevice. Data structures 180 include one or more volume folders 182, oneor more chunk folders 184/185 within the volume folder 182, and multiplefiles within chunk folder 184. Each chunk folder 184/185 includes ametadata file 186/187, a metadata index file 188/189, one or morecontainer files 190/191/193, and a container index file 192/194.Metadata file 186/187 stores non-SI data blocks as well as links to SIdata blocks stored in container files. Metadata index file 188/189stores an index to the data in the metadata file 186/187. Containerfiles 190/191/193 store SI data blocks. Container index file 192/194stores an index to container files 190/191/193. Among other things,container index file 192/194 stores an indication of whether acorresponding block in a container file 190/191/193 is referred to by alink in a metadata file 186/187. For example, data block B2 in thecontainer file 190 is referred to by a link in metadata file 187 inchunk folder 185. Accordingly, the corresponding index entry incontainer index file 192 indicates that data block B2 in container file190 is referred to. As another example, data block B1 in container file191 is referred to by a link in metadata file 187, and so thecorresponding index entry in container index file 192 indicates thatthis data block is referred to.

As an example, data structures 180 illustrated in FIG. 1H may have beencreated as a result of separate secondary copy operations involving twoclient computing devices 102. For example, a first secondary copyoperation on a first client computing device 102 could result in thecreation of the first chunk folder 184, and a second secondary copyoperation on a second client computing device 102 could result in thecreation of the second chunk folder 185. Container files 190/191 in thefirst chunk folder 184 would contain the blocks of SI data of the firstclient computing device 102. If the two client computing devices 102have substantially similar data, the second secondary copy operation onthe data of the second client computing device 102 would result in mediaagent 144 storing primarily links to the data blocks of the first clientcomputing device 102 that are already stored in the container files190/191. Accordingly, while a first secondary copy operation may resultin storing nearly all of the data subject to the operation, subsequentsecondary storage operations involving similar data may result insubstantial data storage space savings, because links to already storeddata blocks can be stored instead of additional instances of datablocks.

If the operating system of the secondary storage computing device 106 onwhich media agent 144 operates supports sparse files, then when mediaagent 144 creates container files 190/191/193, it can create them assparse files. A sparse file is a type of file that may include emptyspace (e.g., a sparse file may have real data within it, such as at thebeginning of the file and/or at the end of the file, but may also haveempty space in it that is not storing actual data, such as a contiguousrange of bytes all having a value of zero). Having container files190/191/193 be sparse files allows media agent 144 to free up space incontainer files 190/191/193 when blocks of data in container files190/191/193 no longer need to be stored on the storage devices. In someexamples, media agent 144 creates a new container file 190/191/193 whena container file 190/191/193 either includes 100 blocks of data or whenthe size of the container file 190 exceeds 50 MB. In other examples,media agent 144 creates a new container file 190/191/193 when acontainer file 190/191/193 satisfies other criteria (e.g., it containsfrom approx. 100 to approx. 1000 blocks or when its size exceedsapproximately 50 MB to 1 GB). In some cases, a file on which a secondarycopy operation is performed may comprise a large number of data blocks.For example, a 100 MB file may comprise 400 data blocks of size 256 KB.If such a file is to be stored, its data blocks may span more than onecontainer file, or even more than one chunk folder. As another example,a database file of 20 GB may comprise over 40,000 data blocks of size512 KB. If such a database file is to be stored, its data blocks willlikely span multiple container files, multiple chunk folders, andpotentially multiple volume folders. Restoring such files may requireaccessing multiple container files, chunk folders, and/or volume foldersto obtain the requisite data blocks.

Using Backup Data for Replication and Disaster Recovery (“LiveSynchronization”)

There is an increased demand to off-load resource intensive informationmanagement tasks (e.g., data replication tasks) away from productiondevices (e.g., physical or virtual client computing devices) in order tomaximize production efficiency. At the same time, enterprises expectaccess to readily-available up-to-date recovery copies in the event offailure, with little or no production downtime.

FIG. 2A illustrates a system 200 configured to address these and otherissues by using backup or other secondary copy data to synchronize asource subsystem 201 (e.g., a production site) with a destinationsubsystem 203 (e.g., a failover site). Such a technique can be referredto as “live synchronization” and/or “live synchronization replication.”In the illustrated embodiment, the source client computing devices 202 ainclude one or more virtual machines (or “VMs”) executing on one or morecorresponding VM host computers 205 a, though the source need not bevirtualized. The destination site 203 may be at a location that isremote from the production site 201, or may be located in the same datacenter, without limitation. One or more of the production site 201 anddestination site 203 may reside at data centers at known geographiclocations, or alternatively may operate “in the cloud.”

The synchronization can be achieved by generally applying an ongoingstream of incremental backups from the source subsystem 201 to thedestination subsystem 203, such as according to what can be referred toas an “incremental forever” approach. FIG. 2A illustrates an embodimentof a data flow which may be orchestrated at the direction of one or morestorage managers (not shown). At step 1, the source data agent(s) 242 aand source media agent(s) 244 a work together to write backup or othersecondary copies of the primary data generated by the source clientcomputing devices 202 a into the source secondary storage device(s) 208a. At step 2, the backup/secondary copies are retrieved by the sourcemedia agent(s) 244 a from secondary storage. At step 3, source mediaagent(s) 244 a communicate the backup/secondary copies across a networkto the destination media agent(s) 244 b in destination subsystem 203.

As shown, the data can be copied from source to destination in anincremental fashion, such that only changed blocks are transmitted, andin some cases multiple incremental backups are consolidated at thesource so that only the most current changed blocks are transmitted toand applied at the destination. An example of live synchronization ofvirtual machines using the “incremental forever” approach is found inU.S. Patent Application No. 62/265,339 entitled “Live Synchronizationand Management of Virtual Machines across Computing and VirtualizationPlatforms and Using Live Synchronization to Support Disaster Recovery.”Moreover, a deduplicated copy can be employed to further reduce networktraffic from source to destination. For instance, the system can utilizethe deduplicated copy techniques described in U.S. Pat. No. 9,239,687,entitled “Systems and Methods for Retaining and Using Data BlockSignatures in Data Protection Operations.”

At step 4, destination media agent(s) 244 b write the receivedbackup/secondary copy data to the destination secondary storagedevice(s) 208 b. At step 5, the synchronization is completed when thedestination media agent(s) and destination data agent(s) 242 b restorethe backup/secondary copy data to the destination client computingdevice(s) 202 b. The destination client computing device(s) 202 b may bekept “warm” awaiting activation in case failure is detected at thesource. This synchronization/replication process can incorporate thetechniques described in U.S. patent application Ser. No. 14/721,971,entitled “Replication Using Deduplicated Secondary Copy Data.”

Where the incremental backups are applied on a frequent, on-going basis,the synchronized copies can be viewed as mirror or replication copies.Moreover, by applying the incremental backups to the destination site203 using backup or other secondary copy data, the production site 201is not burdened with the synchronization operations. Because thedestination site 203 can be maintained in a synchronized “warm” state,the downtime for switching over from the production site 201 to thedestination site 203 is substantially less than with a typical restorefrom secondary storage. Thus, the production site 201 may flexibly andefficiently fail over, with minimal downtime and with relativelyup-to-date data, to a destination site 203, such as a cloud-basedfailover site. The destination site 203 can later be reversesynchronized back to the production site 201, such as after repairs havebeen implemented or after the failure has passed.

Integrating With the Cloud Using File System Protocols

Given the ubiquity of cloud computing, it can be increasingly useful toprovide data protection and other information management services in ascalable, transparent, and highly plug-able fashion. FIG. 2B illustratesan information management system 200 having an architecture thatprovides such advantages and incorporates use of a standard file systemprotocol between primary and secondary storage subsystems 217, 218. Asshown, the use of the network file system (NFS) protocol (or any anotherappropriate file system protocol such as that of the Common InternetFile System (CIFS)) allows data agent 242 to be moved from the primarystorage subsystem 217 to the secondary storage subsystem 218. Forinstance, as indicated by the dashed box 206 around data agent 242 andmedia agent 244, data agent 242 can co-reside with media agent 244 onthe same server (e.g., a secondary storage computing device such ascomponent 106), or in some other location in secondary storage subsystem218.

Where NFS is used, for example, secondary storage subsystem 218allocates an NFS network path to the client computing device 202 or toone or more target applications 210 running on client computing device202. During a backup or other secondary copy operation, the clientcomputing device 202 mounts the designated NFS path and writes data tothat NFS path. The NFS path may be obtained from NFS path data 215stored locally at the client computing device 202, and which may be acopy of or otherwise derived from NFS path data 219 stored in thesecondary storage subsystem 218.

Write requests issued by client computing device(s) 202 are received bydata agent 242 in secondary storage subsystem 218, which translates therequests and works in conjunction with media agent 244 to process andwrite data to a secondary storage device(s) 208, thereby creating abackup or other secondary copy. Storage manager 240 can include apseudo-client manager 217, which coordinates the process by, among otherthings, communicating information relating to client computing device202 and application 210 (e.g., application type, client computing deviceidentifier, etc.) to data agent 242, obtaining appropriate NFS path datafrom the data agent 242 (e.g., NFS path information), and deliveringsuch data to client computing device 202.

Conversely, during a restore or recovery operation client computingdevice 202 reads from the designated NFS network path, and the readrequest is translated by data agent 242. The data agent 242 then workswith media agent 244 to retrieve, re-process (e.g., re-hydrate,decompress, decrypt), and forward the requested data to client computingdevice 202 using NFS.

By moving specialized software associated with system 200 such as dataagent 242 off the client computing devices 202, the illustrativearchitecture effectively decouples the client computing devices 202 fromthe installed components of system 200, improving both scalability andplug-ability of system 200. Indeed, the secondary storage subsystem 218in such environments can be treated simply as a read/write NFS targetfor primary storage subsystem 217, without the need for informationmanagement software to be installed on client computing devices 202. Asone example, an enterprise implementing a cloud production computingenvironment can add VM client computing devices 202 without installingand configuring specialized information management software on theseVMs. Rather, backups and restores are achieved transparently, where thenew VMs simply write to and read from the designated NFS path. Anexample of integrating with the cloud using file system protocols orso-called “infinite backup” using NFS share is found in U.S. PatentApplication No. 62/294,920, entitled “Data Protection Operations Basedon Network Path Information.” Examples of improved data restorationscenarios based on network-path information, including using storedbackups effectively as primary data sources, may be found in U.S. PatentApplication No. 62/297,057, entitled “Data Restoration Operations Basedon Network Path Information.”

Highly Scalable Managed Data Pool Architecture

Enterprises are seeing explosive data growth in recent years, often fromvarious applications running in geographically distributed locations.FIG. 2C shows a block diagram of an example of a highly scalable,managed data pool architecture useful in accommodating such data growth.The illustrated system 200, which may be referred to as a “web-scale”architecture according to certain embodiments, can be readilyincorporated into both open compute/storage and common-cloudarchitectures.

The illustrated system 200 includes a grid 245 of media agents 244logically organized into a control tier 231 and a secondary or storagetier 233. Media agents assigned to the storage tier 233 can beconfigured to manage a secondary storage pool 208 as a deduplicationstore and be configured to receive client write and read requests fromthe primary storage subsystem 217 and direct those requests to thesecondary tier 233 for servicing. For instance, media agents CMA1-CMA3in the control tier 231 maintain and consult one or more deduplicationdatabases 247, which can include deduplication information (e.g., datablock hashes, data block links, file containers for deduplicated files,etc.) sufficient to read deduplicated files from secondary storage pool208 and write deduplicated files to secondary storage pool 208. Forinstance, system 200 can incorporate any of the deduplication systemsand methods shown and described in U.S. Pat. No. 9,020,900, entitled“Distributed Deduplicated Storage System,” and U.S. Pat. Pub. No.2014/0201170, entitled “High Availability Distributed DeduplicatedStorage System.”

Media agents SMA1-SMA6 assigned to the secondary tier 233 receive writeand read requests from media agents CMA1-CMA3 in control tier 231, andaccess secondary storage pool 208 to service those requests. Mediaagents CMA1-CMA3 in control tier 231 can also communicate with secondarystorage pool 208 and may execute read and write requests themselves(e.g., in response to requests from other control media agentsCMA1-CMA3) in addition to issuing requests to media agents in secondarytier 233. Moreover, while shown as separate from the secondary storagepool 208, deduplication database(s) 247 can in some cases reside instorage devices in secondary storage pool 208.

As shown, each of the media agents 244 (e.g., CMA1-CMA3, SMA1-SMA6,etc.) in grid 245 can be allocated a corresponding dedicated partition251A-251l, respectively, in secondary storage pool 208. Each partition251 can include a first portion 253 containing data associated with(e.g., stored by) media agent 244 corresponding to the respectivepartition 251. System 200 can also implement a desired level ofreplication, thereby providing redundancy in the event of a failure of amedia agent 244 in grid 245. Along these lines, each partition 251 canfurther include a second portion 255 storing one or more replicationcopies of the data associated with one or more other media agents 244 inthe grid.

System 200 can also be configured to allow for seamless addition ofmedia agents 244 to grid 245 via automatic configuration. As oneillustrative example, a storage manager (not shown) or other appropriatecomponent may determine that it is appropriate to add an additional nodeto control tier 231, and perform some or all of the following: (i)assess the capabilities of a newly added or otherwise availablecomputing device as satisfying a minimum criteria to be configured as orhosting a media agent in control tier 231; (ii) confirm that asufficient amount of the appropriate type of storage exists to supportan additional node in control tier 231 (e.g., enough disk drive capacityexists in storage pool 208 to support an additional deduplicationdatabase 247); (iii) install appropriate media agent software on thecomputing device and configure the computing device according to apre-determined template; (iv) establish a partition 251 in the storagepool 208 dedicated to the newly established media agent 244; and (v)build any appropriate data structures (e.g., an instance ofdeduplication database 247). An example of highly scalable managed datapool architecture or so-called web-scale architecture for storage anddata management is found in U.S. Patent Application No. 62/273,286entitled “Redundant and Robust Distributed Deduplication Data StorageSystem.”

The embodiments and components thereof disclosed in FIGS. 2A, 2B, and2C, as well as those in FIGS. 1A-1H, may be implemented in anycombination and permutation to satisfy data storage management andinformation management needs at one or more locations and/or datacenters.

Live Browse Cache Management for Faster Live Browsing and File Indexingof Backup Copies, Including Block-Level Backup Copies of VirtualMachines and/or File Systems

An illustrative approach speeds up live browse and file indexingoperations, as well as file-level restores, for block-level backupcopies in a data storage management system. The approach enables livebrowse to start sooner and progress faster and makes live browsefeasible now for backup copies stored on tape. A cache storage area (the“live browse cache”) is used for locally storing and serving key datablocks, thus relying less on retrieving data from the backup copy. Datablocks are preferentially served from the live browse cache rather thanbeing retrieved from the targeted backup copy. The approach is availablefor a variety of data sources and backup copies, including block-levelbackup copies of virtual machines (VMs) and block-level backup copies offile systems (including UNIX-based and Windows-based operating systemsand corresponding file systems). File indexing relies upon an underlyinglive browse operation, and therefore benefits from the presentenhancements to live browse. File-level restores also benefit (i.e.,starting sooner and progressing faster) from retrieving information fromthe live browse cache rather than from backup media as much as possible.

FIG. 3A is a block diagram illustrating some salient portions of asystem 300 for improving performance of live browsing, file indexing,and/or file-level restoring of a block-level backup copy of virtualmachine data, according to an illustrative embodiment. FIG. 3A depicts:VM host 301 comprising hypervisor/VMM 302 and any number of virtualmachines (VMs) 303 in communication with corresponding virtual machinedisks 305 configured in data storage device(s) 304 and comprisingprimary data 112; disk/flash storage device(s) 308 comprising backupcopies 116; tape storage device(s) 309 comprising backup copies 116;cloud service account 310 comprising backup copies 116; data backup andretrieval components 315; and endpoint 321 for user-driven live browseof backup copies 116.

System 300 is a data storage management system analogous to system 100and further comprising features for live browse cache management. Anexemplary data storage management system 300 is supplied by CommvaultSystems Inc., of Tinton Falls, N.J., USA. System 300 illustrativelycomprises components 315, but not necessarily the other depictedcomponents and/or depicted data 112 and 116.

Primary data 112 is generated by and natively accessible by a virtualmachine 303. Primary data 112 for a particular VM 303 is stored in avirtual disk (e.g., VMDK file, VHD file, etc.) 305 configured in primarydata storage device(s) 304. More details on primary data 112 are givenelsewhere herein.

Backup copies 116 are described in further detail elsewhere herein. Ablock-level backup copy 116 as shown in the present figure comprisesdata backed up from a source virtual disk 305. Any number of successiveblock-level backup copies 116 taken at different points in time co-existin system 300. Backup copies 116 as shown in the present figure aregenerated using block-level backup techniques and therefore are referredto as block-level backup copies. Many of the advantages described hereinfor live browse cache management are achieved in the context ofblock-level backup operations and block-level backup copies 116. Moredetails on block-level storage operations and backup copies 116 arefound elsewhere herein.

Virtual machine (VM) host 301 is a computing device (e.g., VM server)comprising one or more hardware processors and computer memory. VM hostsare well known in the art. VM host 301 runs a hypervisor or virtualmachine monitor (VMM), e.g., 302, that in turn manages any number of VMs303 hosted by VM host 301. In some embodiments, VM host 301 is notexpressly accessible, as it is part of a cloud computing infrastructureunderlying a cloud services account, but VMs 303 are instantiated andactivated in the cloud services account.

Hypervisor or virtual machine monitor (VMM) 302 is well known in the artand manages any number of VMs 303 as well as their access to primarydata 112 in respective virtual disks 305.

Virtual machines 303 are well known in the art. VMs 303 are hosted by VMhost 301. Each VM 303 generates and uses primary data 112 in acorresponding virtual disk 305. In some embodiments, VMs 303 run in acloud services account as part of a cloud computing infrastructure.

Data storage device(s) 304 are analogous to data storage device 104 andare well known in the art. One or more data storage devices 304 areconfigured to store primary data 112 for VMs 303. In some embodiments,data storage resources 304 are configured in a cloud services account aspart of a cloud computing infrastructure.

Virtual machine disks 305 are also known as “virtual disks.” VM disksare well known in the art. For example, VMDK (virtual machine disk)files describe containers for virtual machine hard disk drives used byVMs. Likewise, VHD (virtual hard disk) files. Different VM systems usedifferent virtual machine disk formats. Thus, the terms VMDK file andVHD file are used synonymously herein with reference to VM disk 305,because of their one-to-one correspondence. For example, a VMWare VM 303uses a VMDK file as its VM disk 305.

Data storage device(s) 308 comprise hard disk and/or flash storagetechnology and are considered to be relatively fast at providing randomaccess to data stored thereon. Disk/flash storage devices 308 are wellknown in the art. Any number of backup copies 116 are stored thereon.

Data storage device(s) 309 comprise storage tape technology that is wellknown in the art. However, unlike disk and flash, tape is accessiblesequentially, which is what accounts for its unacceptably slowperformance characteristics (in the prior art) in regard torandom-access features such as live browse. Using the illustrative livebrowse cache enables speedier live browse and makes it feasible to livebrowse block-level backup copies stored on tape 309.

Cloud service account 310 is well known in the art (e.g., Amazon WebServices, Microsoft Azure, etc.). Cloud service accounts 310 includedata storage resources (cloud-based storage) rated at different rates ofresponsiveness. Cloud-based storage provides random access to datastored therein, but empirical experience indicates that the kind ofrandom access needed in live browsing operations is unacceptably slow.Using the illustrative live browse cache enables speedier live browseand makes it feasible to live browse backup copies stored in cloudservice accounts 310.

Data backup and retrieval components 315 comprise a number of componentsthat are not shown in detail in the present figure for the sake ofsimplicity. More details are given in FIG. 4 .

Endpoint 321 is a computing device well known in the art for providing auser with live browse access to block-level backup copies 116. Endpoint321 can be a laptop, a desktop, a tablet, a web access terminal, etc.,without limitation. A user is typically provided with access to system300 and the user can choose, via a user interface presented on endpoint321, to live browse a certain backup copy 116.

System 300 is not limited to the present depiction. In otherembodiments, system 300 also comprises application host 311 andassociated components as shown in FIG. 3B. Additionally oralternatively, system 300 also comprises any number of other componentsshown in preceding figures herein. In some embodiments, only components315 are part of system 300, whereas the other depicted components areserviced thereby and/or are associated therewith without being part ofsystem 300.

FIG. 3B is a block diagram illustrating some salient portions of asystem 300 for improving performance of live browsing, file indexing,and/or file-level restoring of a block-level backup copy of file systemdata, according to an illustrative embodiment. The present figuredepicts: application host 311 comprising file manager 313 and any numberof applications 110 in communication with file system 314 configured indata storage device(s) 304 and comprising primary data 112; disk/flashstorage device(s) 308 comprising backup copies 116; tape storagedevice(s) 309 comprising backup copies 116; cloud service account 310comprising block-level backup copies 116; data backup and retrievalcomponents 315; and endpoint 321 for user-driven live browse ofblock-level backup copies 116.

Applications 110 are well known in the art and are described in moredetail elsewhere herein. There is no limit on how many applications 110execute on and are hosted by application host 311.

Application host 311 is a computing device (e.g., server) comprising oneor more hardware processors and computer memory. Application hosts arewell known in the art.

File manager (or file browser) 313 is an application or computer programthat executes on application host 311 and provides users with access tofiles and folders in file system 314. Microsoft Windows Explorer is anexample of file manager 313, without limitation. File manager 313 iswell known in the art.

File system 314 is well known in the art and organizes data stored instorage device(s) 304 and controls how data is stored thereto andretrieved therefrom. Examples of file systems include New TechnologyFile System (NTFS), UNIX and related UNIX-based solutions. Otherexamples without limitation include FAT (FAT12, FAT16, FAT32), exFAT,HFS, HFS+, HPFS, APFS, UFS, ext2, ext3, ext4, XFS, btrfs, ISO 9660,Files-11, Veritas File System, VMFS, ZFS, ReiserFS and UDF (source: FileSystem, Wikipedia, https://en.wikipedia.org/wiki/File system, accessed8/19/2019). The illustrative live browse cache management works with anyand all source (primary data) file systems. As explained in more detailelsewhere herein, certain advantages accrue when the data agentassociated with the source data has the ability to interpret at leastpart of the source file system at backup time. When the source filesystem is not discernible to the data agent, techniques disclosed hereinhelp to collect information that is used in second and subsequentoperations to speed up live browse and file indexing.

System 300 is not limited to the present depiction. In otherembodiments, system 300 also comprises VM host 301 and associatedcomponents as shown in FIG. 3A. Additionally or alternatively, system300 also comprises any number of other components shown in precedingfigures herein.

FIG. 4 is a block diagram illustrating some details of data backup andretrieval components 315 in system 300. FIG. 4 depicts: primary data112, block-level backup copy 116, endpoint 321, and a number of databackup and retrieval components 315, including storage manager 440, dataagent 442, media agent 444, and pseudo-disk driver 456.

Data backup and retrieval components 315 are supplied by CommvaultSystems, Inc. of Tinton Falls, N.J., USA.

Storage manager 440 is analogous to storage manager 140 and additionallycomprises features for operating in system 300, e.g., triggering fileindexing operations, indicating to a data agent 442 that media agent 444uses live browse cache management, etc. Storage manager 440 isillustratively embodied as executable software that executes on anunderlying computing device comprising one or more hardware processorsand computer memory. In some embodiments, storage manager 440 comprisesa computing device comprising one or more hardware processors andcomputer memory.

Data agent 442 is analogous to data agent 142 and further comprisesfeatures for operating in system 300, e.g., flagging cacheable datablocks, querying media agent(s) for indications on which source datablocks are cacheable, etc. Data agent 442 is associated with andspecialized for handling backups from a certain kind of data source,i.e., specialized for different kinds of primary data 112. Exemplarydata agents 442 include Virtual Server Agent (“VSA”), and various filesystem data agents, e.g., Windows File System Agent, UNIX/Linux FileSystem Agent, etc. In some embodiments, data agent 442 executes on thesame host computing device as the data source; for example, VM host 301also executes VSA data agent 442 running on one of the VMs 303; forexample, application host 311 also executes a file system data agent 442suitable to and compatible with file system 314. In other embodiments,data agent 442 executes on a separate computing device distinct fromhosts 301/311 and from media agent 444's host; in some embodiments, dataagent 442 is co-located with media agent 444 on the same host computingdevice.

Media agent 444 is analogous to media agent 144 and further comprisesfeatures for operating in system 300, e.g., cache management logic,enhanced backup logic that adds cacheable flags to a backup block index,enhanced retrieval logic that preferentially serves data from the livebrowse cache, the live browse cache, live browse cache index, and heatmap. Media agent 444 comprises a computing device (not shown) thatcomprises one or more hardware processors and computer memory forexecuting computer programs, as well as cache storage technology foraccommodating the live browse cache. In some embodiments, the underlyingcomputing device also hosts a data agent 442 and/or a pseudo-disk driver456 in addition to hosting media agent 444.

Pseudo-disk driver 456 is a driver that presents a pseudo-disk tolive-browse users. Pseudo-disk driver 456 requests data blocks usingread requests based on live browse actions taken by a user. Pseudo-diskdriver 456 (a/k/a “CVBLK” and/or “pseudo-mount”) is described in moredetail in U.S. Pat. No. 9,852,026, entitled “Efficient ApplicationRecovery based on a Pseudo-Storage-Device Driver,” which is incorporatedby reference herein. In some embodiments, pseudo-disk driver 456 residesand executes on the same computing device that hosts media agent 444. Inother embodiments, pseudo-disk driver resides and executes on a separatecomputing device comprising one or more hardware processors and computermemory, which is interposed between endpoint 321 and media agent 444,and which in some embodiments is referred to as a File Recovery Enablerfor Linux (“FREL”). FRELs are used when the operating system involved ingenerating the source primary data 112 (e.g., Linux) is different fromthe operating system underlying media agent 444 (e.g., Windows); in sucha configuration, the FREL acts as a bridge enabling the backup copy tobe mounted to the media agent host and live browsed therefrom. FRELs asdescribed by Commvault Systems, Inc. are well known in the art.

The bold arrows in the present figure show logical data flows among thedepicted components. The present figure depicts some of the keycomponents that make possible one or more of the illustrativeembodiments. The embodiments are not limited to the depictedconfiguration. Generally, system 300 comprises one storage manager 440responsible for managing storage operations within system 300, and anynumber of data agents 442, media agents 444, and/or pseudo-disk drivers456. VM hosts 301, application hosts 311, primary data storage 304, andbackup media 308, 309, and 310 are not necessarily part of system 300,but system 300 interfaces/interoperates with any number thereof.

FIG. 5 is a block diagram illustrating certain operations and data flowsin a block-level backup in system 300, wherein the type of sourcevirtual machine/file system is known to the originating data agent 442.In this configuration, data agent 442 recognizes certain key aspects ofsource file system 314 or source VM disk 305 that are relevant to livebrowse cache management. See also FIG. 9 . FIG. 5 depicts a block-levelbackup operation, e.g., full, incremental, differential, etc. FIG. 5depicts: primary data 112 (organized by a file system known to dataagent 442); block-level backup copy 116 stored in backup media (e.g.,308, 309, 310) along with index 546; data agent 442 comprisingflag-setting logic 542; and media agent 444 comprising logic 544, index546, cache management logic 555, live browse cache index 556, and livebrowse cache 557. Logical data flows and information pathways aredepicted by arrows.

Flag-setting logic 542 is a functional component of data agent 442, andis responsible at least in part for determining which data blocks insource primary data 112 are of a kind (i.e., cacheable) that should beadded to live browse cache 557, e.g., file-system descriptor datablocks, without limitation. This aspect works with source file systemsthat are known to and understood by data agent 442. When the source filesystem is unknown to data agent 442, FIGS. 8A and 8B describe operationsneeded for live browse cache management. Flag-setting logic 542indicates to media agent 444 which data blocks being backed up should beflagged as live-browse cacheable.

Logic 544 is a functional component of media agent 444 that isresponsible at least in part for receiving data blocks from data agent442, further processing them (e.g., compression, encryption,deduplication, formatting, etc.), generating block-level backup copies116, and storing copies 116 to backup media (e.g., 308, 309, 310). Logic544 is further responsible for tracking where data blocks are stored onbackup media, e.g., file location, block offset, etc., and for addingthis information to index 546. Logic 544 is further responsible forreceiving information from data agent 442 on whether certain data blocksare live-browse cacheable and adds this information to index 546,illustratively in the form of flags associated with the cacheable datablocks. Logic 544 is further responsible for associating index 546 withbackup copy 116 and for storing index 546 to backup media. In someembodiments, logic 544 parses out flagged (cacheable) data blocksreceived from data agent 542 and transmits them (not shown here) tocache management logic 555.

Backup block index and flags 546 (or “index 546” or “flags 546”) is adata structure created and maintained by logic 544. As noted, index 546comprises location-related information about each backed up data blockand further comprises flags for live-browse cacheable data blocks. Inembodiments where index 546 is a table, cacheable flag tracking isimplemented as an added column in the table, though the invention is notso limited.

Cache management logic 555 is a functional component of media agent 444that is responsible at least in part for a variety of functions relatingto live browse cache 557, including receiving data blocks, parsing outdata blocks that are live-browse cacheable, checking whether each datablock is already in live browse cache 557 (e.g., by checking index 556),and if not, adding the data block to live browse cache 557. In someembodiments, the data blocks are pre-parsed by and received from logic544 (not shown here). Cache management logic 555 associates each datablock with a data source (e.g., a certain VM and/or data file) and/orwith a particular point-in-time and backup copy 116. Cache managementlogic 555 is also responsible for adding to cache 557 data blocks thathave changed as identified by an incremental/differential backupoperation, e.g., retaining data block D from a prior backup and addingchanged block D′ generated by the present backup operation. Cachemanagement logic 555 also is responsible for pruning live browse cache557 when storage space begins to run short.

Live browse cache index (“LBC index”) 556 is a data structure,illustratively maintained by logic 555, that tracks data blockidentifiers and their associations as stored in live browse cache 557.LBC index 556 is consulted for purposes of deduplication, i.e., toprevent the same unchanged data block from being repeatedly stored toLBC 557, and for look-up during live browse operations to find outwhether a data block in a read request is stored in and can be servedfrom live browse cache 557.

Live browse cache (“LBC”) 557 is a data storage area configured on thecomputing device that hosts media agent 444. LBC 557 stores data blocksthat are live-browse cacheable. Cache management logic 555 maintains LBC557, e.g., adding to LBC 557, pruning LBC 557, updating LBC index 556based on changes to LBC 557, etc.

Several numbered steps depicted in the present figure illustrate some ofthe data processing logic that occurs in system 300 in a block-levelbackup operation (e.g., full, incremental, differential), wherein thetype of source virtual machine/file system is known to the originatingdata agent 442. Step 1 occurs in the course of a block-level backupoperation involving data agent 442 and media agent 444. In someembodiments, storage manager 440 triggers the block-level backupoperation by instructing data agent 442 and media agent 444 accordingly.In the present scenario, data agent 442 knows and understands the filesystem that governs the source primary data 112. At step 1, data agent442 extracts a data block D (or a grouping of data blocks grouped intoan “extent” E) from primary data 112. Data agent 442 (e.g., usingflag-setting logic 542) determines whether data block D should beflagged as live-browse cacheable, based on determining whether it is afile-system descriptor data block (e.g., MFT, superblock, etc.). Dataagent 442 flags file-system descriptor blocks as live-browse cacheable.

At step 6 (the present figure depicts no steps 2-5), data agent 442transmits data block D to media agent 444, along with an indication ofwhether the data block is cacheable, if applicable. At step 6, mediaagent 444 delivers data block D to logic 544 and logic 555. In someembodiments, data block D is delivered to cache management logic 555only if accompanied by a cacheable flag. In some embodiments, data blockD is delivered to cache management logic 555 by logic 544 (not by dataagent 442) after logic 544 determines that data block D is accompaniedby a cacheable flag.

At step 7, after logic 544 processes block D for inclusion within backupcopy 116 as is well known in the art, logic 544 stores block-levelbackup copy 116 to backup media, e.g., disk/flash 308, tape 309, and/orcloud service account 310. At step 8, logic 544 populates backup blockindex 546 with storage information about data block D, and adds acacheable flag, if applicable, to mark block D in index 546. At step 9,media agent 444 (e.g., using logic 544) copies index 546 to backup media(e.g., 308, 309, and/or 310). In some embodiments, index 546 is storedto the same backup media as backup copy 116, because they are associatedwith each other, but the invention is not so limited.

At step 10, cache management logic 555 analyzes data block D, includingchecking LBC index 556 to determine whether data block D is alreadypresent in LBC 557. In some embodiments, deduplication logic in cachemanagement logic 555 will account for data block D without storinganother copy thereof in live browse cache 557. Accordingly, each datablock added to LBC 557 will receive a unique signature, e.g., based on ahash function applied in a manner well known in the art. Thededuplication logic will audit a candidate data block against existingsignatures tracked in LBC index 556 to determine whether the candidateblock is unique or duplicative, and duplicative data blocks will not beadded to LBC 557. A new version of a certain data block associated witha certain data source (e.g., VM, virtual disk, file system, etc.), i.e.,modified data block D′, is treated as a new block, which is associatedwith a later backup copy 116 of the same data source as the originaldata block D. Data blocks received without a cacheable flag are notchecked against index 556, as they are not candidates for live browsecache 557 at this stage.

At step 11, data blocks that meet criteria for being added to the livebrowse cache, i.e., cacheable flag, not duplicative, etc., are added tolive browse cache 557 by cache management logic 555. At step 12, cachemanagement logic 555 updates LBC index 556 to reflect the addition ofdata blocks to live browse cache 557.

Steps 1 and 6-12 are included here to enhance the reader's understandingof the present disclosure, but the invention is not so limited. Otherembodiments implement different sequences of events and/or perform someof the depicted steps concurrently and/or include fewer or additionalsteps not shown here. Furthermore, data agent 442 and media agent 444are not limited to the functionality and data structures depicted in thepresent figure.

FIG. 6 is a block diagram illustrating certain operations and data flowsin a user-driven live browse operation that follows the block-levelbackup operations of FIGS. 5 and/or 8A/8B. The present figure depicts:block-level backup copy 116; live browse endpoint 321; media agent 444comprising index 546, cache management logic 555, LBC index 556, LBC557, mount point 643, retrieval logic 644, and heat map 646; andpseudo-disk driver 456 comprising pseudo-disk 656, which comprisesrecall store 658 and private store 659, and I/O buffer 657. Logical dataflows and information pathways are depicted by arrows.

Mount point 643 is a directory/folder configured on media agent 444 toaccess via the media agent's file system a backup copy, such asblock-level backup copy 116. Mount points and techniques for mounting abackup copy to a computing device are well known in the art.

Retrieval logic 644 is a functional component of media agent 444 and isgenerally responsible for mounting a targeted backup copy 116, receivingread requests from pseudo-disk driver 456 (or from other entities),determining the optimal source for recalling each data block in responseto the read requests, recalling each data block from the optimal source,and serving the recalled data block in response to the read request. Todetermine the optimal source, logic 644 checks LBC index 556 todetermine whether the data block is present in live browse cache 557; ifnot found there, logic 644 mounts backup copy 116 to mount point 643 (ifnot already mounted) and recalls the data block from backup copy 116,e.g., using index 546 to quickly locate data blocks on backup media.

Heat map 646 is a data structure illustratively maintained by retrievallogic 644 to indicate how often each recalled data block has been read,e.g., how many read requests over a certain time period. Frequentlyrecalled data blocks will be preferentially preserved in the live browsecache longer than rarely recalled ones when live browse cache 557 ispruned.

Pseudo-disk driver 456 comprises pseudo-disk 656 and I/O buffer 657.Live browse commands from endpoint 321 are submitted via I/O buffer 657.Pseudo-disk driver 456 determines whether the command, e.g., a readrequest for a data block D, can be served from recall store 658 orprivate store 659. Write requests are written to private store 659. Seealso U.S. Pat. No. 9,852,026, entitled “Efficient Application Recoverybased on a Pseudo-Storage-Device Driver,” for more details on how anillustrative pseudo-disk operates. In the present embodiments,pseudo-disk driver 456 operates as an intermediary between live browseendpoint 321 and media agent 344, using recall store 658 to transmitread requests to media agent 444 and receive responses therefrom. Insome embodiments, no pseudo-disk driver is configured and insteadendpoint 321 interfaces directly with media agent 444, requesting readsand presenting results to the endpoint's user.

Several numbered steps depicted herein illustrate some of the dataprocessing logic that occurs in system 300 during a user-driven livebrowse operation. Illustratively the live browse operation follows thebackup operation depicted in FIG. 5 (wherein data agent 442knows/recognizes the primary data's file system) and/or FIGS. 8A/8B(wherein data agent 442 does not know/recognize the primary data's filesystem). Distinctions between the scenarios of FIG. 5 versus FIGS. 8A/8Bare described here and in FIGS. 9 and 10A/10B.

At step 1, a read request comes in from live browse endpoint 321. Thelive browse operation in this scenario is user-driven, which includesselections made by a user into a user interface, e.g., navigating downthe branch of a letter drive and file folder/directory tree. At step 2,the read request is transmitted to media agent 444, e.g., from recallstore 658 to retrieval logic 644. Retrieval logic 644 analyzes the readrequest to determine the identity of data block D being requested.Retrieval logic 644 consults LBC index 556 to determine whether datablock D is in the live browse cache 557, and if so, at step 3, retrievallogic 644 retrieves data block D from LBC 557. If data block D is not inLBC 557, retrieval logic 644 mounts backup copy 116 at step 4 (if notalready mounted) and retrieves data block D from backup copy 116 at step5, e.g., using index 546 to locate the data blocks in backup media. Atstep 6, the requested data block D is in the possession of retrievallogic 644, which serves data block D in response to the read requestthat originated with live browse endpoint 321.

In some embodiments, before the user has an opportunity to generate anyread requests, retrieval logic 644 pre-fetches flagged data blocks tospeed up the user's live browse experience. For example, on receivingnotice that a live browse of a certain backup copy 116 has beeninitiated by a user at endpoint 321, retrieval logic 644 consults index546 (step 2B) to identify all data blocks in backup copy 116 that wereflagged as live-browse cacheable in the preceding backup operation (see,e.g., FIGS. 5 and 8B). Equipped with this information, retrieval logic644 preferentially retrieves the identified data blocks from LBC 557 andif not found there, retrieves them from block-level backup copy 116 asdescribed in the preceding paragraph. Additionally, retrieval logic 644conducts the retrieval from backup copy 116 by defining a sequentialorder for the data blocks to be retrieved and retrieving them accordingto the sequential order, which minimizes delays in accessing backupmedia, especially cloud-based storage and tape. Retrieval logic 644transmits retrieved data blocks to recall store 658 and issues a releasecommand to endpoint 321 to permit the intake of user commands. Becausethe recall store 658 is pre-populated with many, if not all, data blocksneeded to begin the live browse operation, the user experiences in someembodiments an “instant on” live browse operation. From this pointonward, the live browse proceeds as described in the precedingparagraph, with each user-driven read request being analyzed and servedon demand.

The present figure does not include step 7. At step 8, retrieval logic644 populates one or more entries in heat map 646 to indicate which datablock D was retrieved in the present read request. Heat map 646 is alsopopulated during the pre-fetch operations described in the precedingparagraph. Thus, heat map 646 reflects each retrieval of each datablock, whether the data block was retrieved from LBC 557 or fromblock-level backup copy 116. At step 9, retrieval logic 644 transmitsdata block D to cache management logic 555 for analysis. As described inFIG. 5 in regard to steps 10, 11, and 12, data block D is added to LBC557 if not already therein and LBC index 556 is updated accordingly.

Steps 1-6 and 8-12 are included here to enhance the reader'sunderstanding of the present disclosure, but the invention is not solimited. Other embodiments implement different sequences of eventsand/or perform some of the depicted steps concurrently. Furthermore,pseudo-disk driver 456 and media agent 444 are not limited to thefunctionality and data structures depicted in the present figure.

FIG. 7 is a block diagram illustrating certain operations and data flowsin a file indexing operation that follows the block-level backup ofFIGS. 5 and/or 8A/8B. The present figure depicts: block-level backupcopy 116; storage manager 440; media agent 444 comprising index 546,cache management logic 555, LBC index 556, LBC 557, mount point 643,retrieval logic 644, heat map 646, file indexing logic 744, and fileindex 746. Logical data flows and information pathways are depicted byarrows.

File indexing logic 744 is a functional component of media agent 444,which is responsible for discovering all data files backed up withinbackup copy 116 and creating an index (e.g., 746) that tracks where eachfile can be found therein, e.g., filename, copy 116 identifier, copy 116location on storage media, file offset, etc. Notably, the block-levelbackup operation that created backup copy 116 did not capture fileidentities, because it was not a file-level operation, hence the needfor the present file indexing operation. File indexing logic 744initiates a live browse operation and traverses the directory tree todiscover all files backed up within each block-level backup copy 116.Thus, file indexing logic 744 scans the entire directory tree in backupcopy 116 through the live browse mount point 643. File indexing logic744 generates an association between file index 746 and block-levelbackup copy 116.

File index 746 is a data structure created by a file indexing operationand is illustratively populated by media agent 444, e.g., using fileindexing logic 744. In some embodiments, media agent 444 copies fileindex 746 to storage media (not shown here).

Several numbered steps depicted herein illustrate some of the dataprocessing logic that occurs in a file indexing operation in system 300.In some embodiments, file indexing immediately follows the completion ofa block-level backup operation as depicted in FIGS. 5 and 8A/8B, but theinvention is not so limited, and a substantial time lag can elapsebetween backup completion and file indexing. During that time gap, anynumber of user-driven live browse operations can occur, withoutlimitation (see, e.g., FIG. 6 ). In short, file indexing and user-drivenlive browsing are mutually independent operations and neither dependsupon the other.

At step 1, storage manager 440 initiates a file indexing operation for atargeted block-level backup copy 116, e.g., sending instructions tomedia agent 444, which invokes file indexing logic 744. File indexinglogic 744 in turn invokes an internal live browse operation that willtraverse the entire tree within the targeted backup copy 116, e.g.,identifying drive letters, folders/directories, and individual files. Atstep 2, file indexing logic 744 transmits to retrieval logic 644 anindication that an internal live browse has been started, followed by asequence of read requests that are analogous to read requests invoked bya user-driven live browse. As described in more detail in FIG. 6 , atsteps 3-6 retrieval logic 644 pre-fetches data blocks preferentiallyfrom LBC 557 and sequentially from backup copy 116 and transmits resultsto file indexing logic 744, followed by on-demand retrieval as the readrequests come in from file indexing logic 744 (step 2). Step 2B providesretrieval logic 644 with information about the location on backup mediaof backed up data blocks; relevant file location information is passedto file indexing logic 744 at step 6 for adding to file index 746.

At step 7, file indexing logic 744 processes the received data blocksand location information and populates file index 746 accordingly.

Steps 8-12 are analogous to steps 8-12 in FIG. 6 , i.e., populating heatmap 646, adding data blocks to LBC 557, and updating LBC index 556.

Steps 1-12 are included here to enhance the reader's understanding ofthe present disclosure, but the invention is not so limited. Otherembodiments implement different sequences of events and/or perform someof the depicted steps concurrently. Furthermore, storage manager 440 andmedia agent 444 are not limited to the functionality and data structuresdepicted in the present figure.

FIG. 8A is a block diagram illustrating certain operations and dataflows in a block-level backup (Full Backup) in system 300, wherein thetype of source virtual machine/file system is unknown to the originatingdata agent 442. In contrast to FIG. 5 , where originating data agent 442has an understanding of and an ability to interpret the file system thatgoverns primary data 112 being backed up, no such capability exists inthe present scenario. In other words, data agent 442 is aware of theprimary data 112 it needs to back up, but lacks the ability to interpretthe primary data to determine which data blocks are candidates for livebrowse caching, e.g., file-system descriptor blocks. In the presentfigure, when a full block-level backup is triggered, data agent 442illustratively lacks most or even all interpretive information about thedata blocks it is backing up from primary data 112. As a result,relatively little information is collected in this full backup operationas it relates to live browse, as illustrated by several skipped or nullsteps depicted here with dotted outlines, e.g., 2, 3, 5, 10, 11, and 12.However, subsequent user-driven live browse (FIG. 6 ) and file indexing(FIG. 7 ) of block-level backup copy 116 created in the present fullbackup will populate live browse cache 557 and enable these additionalsteps in a subsequent incremental or differential backup of the samesource primary data 112, as shown in FIG. 8B. See also FIG. 10A/10B.

FIG. 8A depicts: primary data 112 undergoing a full block-level backup;block-level backup copy 116 and backup block index 846 (minus LBC-flags)on backup media 308/309/310; data agent 442 comprising flag-settinglogic 542; and media agent 444 comprising logic 544, cache managementlogic 555, LBC index 556, LBC 557, backup block index 846 (minusLBC-flags). Logical data flows and information pathways are depicted byarrows.

Backup block index 846 is analogous to index 546 described in an earlierfigure herein, but lacks the cacheable flags associated with backed updata blocks. The reason for the lacking flags is that data agent 442lacks the capacity to identify cacheable data blocks in the sourceprimary data 112 (contrast to FIG. 5 ). Furthermore, no historicalinformation from previously cached blocks in LBC 557 can be exploitedhere (e.g., by consulting LBC index 556), because a full backupoperation backs up data “from scratch” without reference to earlierbackups. Thus, without being able to refer to live browse cache contentsand without knowing the kinds of data blocks it is backing up in thefull backup, data agent 442 lacks the ability to flag data blocks forcacheability and thus no cacheable flags are populated into backup blockindex 846. Logic 544 copies backup block index 846 to backup media,e.g., 308, 309, 310. Logic 544 associates index 846 with block-levelbackup copy 116 created in the full backup operation.

Several numbered steps depicted in the present figure illustrate some ofthe data processing logic that occurs in system 300 in a fullblock-level backup operation wherein the type of source virtualmachine/file system is unknown to the originating data agent 442. Steps1, 6, 7, 8, and 9 are described in further detail, whereas steps 2, 3,5, 10, 11, and 12 are skipped here or are null (i.e., no data isactually exchanged).

Step 1 occurs in the course of a full block-level backup operationinvolving data agent 442 and media agent 444. In some embodiments,storage manager 440 triggers the backup operation by instructing dataagent 442 and media agent 444 accordingly. At step 1, data agent 442extracts a data block D (or a grouping of data blocks grouped into an“extent” E) from primary data 112. Data agent 442 comprises flag-settinglogic 542, which cannot determine whether data block D should be flaggedas live-browse cacheable, e.g., based on determining whether it is afile-system descriptor data block such as MFT, superblock, etc.

Steps 2, 3, and 5 (which are described in more detail in FIG. 8B) areskipped or result in no additional information being returned to dataagent 442. At step 6, media agent 444 delivers data block D to logic544. In some embodiments, data block D is delivered to cache managementlogic 555 only if accompanied by a cacheable flag, and since no flag isavailable here, no such data blocks are delivered to logic 555. In someembodiments, data block D is delivered to cache management logic 555 bylogic 544 (not by data agent 442) after logic 544 determines that datablock D is accompanied by a cacheable flag. Again, since no flag isavailable here, no such data blocks are delivered to logic 555.

At step 7, after logic 544 processes block D for inclusion within backupcopy 116 as is well known in the art, logic 544 stores block-levelbackup copy 116 to backup media, e.g., disk/flash 308, tape 309, and/orcloud service account 310. At step 8, logic 544 populates backup blockindex 846 with storage information about data block D, but no associatedcacheable flags. At step 9, media agent 444 (e.g., using logic 544)copies index 546 to backup media (e.g., 308, 309, and/or 310). In someembodiments, index 546 is stored to the same backup media as backup copy116, because they are associated with each other, but the invention isnot so limited.

Any data blocks that reach cache management logic 555 (e.g., using step2) are analyzed by logic 555 for whether they are flagged, and discardedif unflagged, thus never reaching steps 10, 11, and 12. As in FIG. 5 ,data blocks received without a cacheable flag are not checked againstindex 556, as they are not candidates for the live browse cache at thisstage.

Steps 1, 6, 7, 8, and 9 are included here to enhance the reader'sunderstanding of the present disclosure, but the invention is not solimited. Other embodiments implement different sequences of eventsand/or perform some of the depicted steps concurrently and/or includefewer or additional steps not shown here. Furthermore, data agent 442and media agent 444 are not limited to the functionality and datastructures depicted in the present figure.

FIG. 8B is a block diagram illustrating certain operations and dataflows in a block-level backup (Incremental or Differential Backup) insystem 300, wherein the type of source virtual machine/file system isunknown to the originating data agent 442.

In contrast to FIG. 5 , where originating data agent 442 has anunderstanding of and the ability to interpret the file system thatgoverns primary data 112 being backed up, no such capability exists inthe present scenario. In other words, as in FIG. 8A, data agent 442 isaware of the primary data 112 it needs to back up, but lacks the abilityto interpret the primary data to determine which data blocks arecandidates for live browse caching, e.g., file-system descriptor blocks.In the present figure, when an incremental or differential block-levelbackup is triggered, data agent 442 has the capacity to track changeddata blocks as against a preceding full backup of the same sourceprimary data 112 (see FIG. 8A), but data agent 442 lacks most or evenall interpretive information about the data blocks it is backing up fromprimary data 112. User-driven live browse (FIG. 6 ) and file indexing(FIG. 7 ) of block-level backup copy 116 created in a preceding fullbackup (FIG. 8A) will populate live browse cache 557 and enable thepresent incremental or differential backup of the same source primarydata 112 to benefit from the live browse cache enhancements herein. Seealso FIG. 10A/10B.

As a result, some of the null/skipped steps in FIG. 8A are enabled hereby one or more intervening live browse and/or file indexing operationsapplied to the full backup copy created in FIG. 8A, i.e., in a precedingbackup operation. Thus, every live browse and/or file indexing appliedto a backup copy, whether full, incremental, or differential, is anopportunity to populate the live browse cache and/or generate cacheableflags that can be used by a later incremental or differential backupoperation.

FIG. 8B depicts: primary data 112 undergoing a differential and/orincremental block-level backup; block-level backup copy 116 and backupblock index 848 (including cacheable flags) on backup media 308/309/310;data agent 442 comprising flag-setting logic 542; and media agent 444comprising logic 544, cache management logic 555, LBC index 556, LBC557, backup block index 848 (including cacheable flags), and backupblock index 848P (including cacheable flags) created in a previousblock-level backup operation. Logical data flows and informationpathways are depicted by arrows.

Backup block index 848P is analogous to backup block index 848, but isassociated with an earlier backup copy 116 that was created in aprevious block-level backup operation, e.g., incremental, differential,which included adding cacheable flags to the backup block index.

Several numbered steps depicted in the present figure illustrate some ofthe data processing logic that occurs in system 300 in an incremental ordifferential block-level backup operation wherein the type of sourcevirtual machine/file system is unknown to the originating data agent442.

Step 1 occurs in the course of an incremental or a differentialblock-level backup operation involving data agent 442 and media agent444. In some embodiments, storage manager 440 triggers the backupoperation by instructing data agent 442 and media agent 444 accordingly.At step 1, data agent 442 extracts a data block D (or a grouping of datablocks grouped into an “extent” E) from primary data 112. In anincremental backup, data agent 442 extracts certain data blocks D′ thatit determines have changed as compared to an immediately precedingbackup operation (e.g., full, incremental). In a differential backup,data agent 442 extracts certain data blocks D′ that changed as comparedto the most recent full backup operation. Thus, by definition, bothincremental and differential backup operations follow a precedingbackup. To the extent that one or more live browse/file indexingoperations intervened between the preceding backup and the presentincremental/differential, the present backup operation will benefit fromdata blocks present in live browse cache 557, even though data agent 442lacks the ability to recognize cacheable flags in the source primarydata 112.

Data agent 442 comprises flag-setting logic 542, but it cannot determinewhether changed data block D′ should be flagged as live-browsecacheable, e.g., based on determining whether it is a file-systemdescriptor data block such as MFT, superblock, etc. To overcome thisdeficiency, at step 2 data agent 442 (e.g., using flag-setting logic542) queries media agent 444 (e.g., cache management logic 555) for alist of data blocks present in live browse cache 557—data blocks thatwere previously backed up from the same primary data source 112, e.g.,VM and/or file system. At step 3, cache management logic 555 obtainsthis information from LBC index 556, and/or at step 4 checks forcacheable flags in backup block index 848P created for the precedingbackup copy 116. Cache management logic 555 formulates a response todata agent 442 that identifies a union of all data blocks identifierspreviously cached and/or flagged and associated with the present primarydata 112. At step 5, cache management logic 555 transmits the responseto data agent 442. Data agent 442 (e.g., using flag-setting logic 542)flags any extracted data blocks D′ based on the response received frommedia agent 444. Thus, if a certain changed data block D′ has acorresponding data block D in live browse cache 557 and/or flagged inindex 848P, then data agent 442 flags data block D′ as cacheable to thelive browse cache.

Steps 6-12 are analogous to their counterparts in FIG. 5 . Thus, at step6, media agent 444 delivers data block D′ to logic 544. In someembodiments, data block D′ is delivered to cache management logic 555only if accompanied by a cacheable flag. In some embodiments, data blockD′ is delivered to cache management logic 555 by logic 544 (not by dataagent 442) after logic 544 determines that data block D′ is accompaniedby a cacheable flag. At step 7, after logic 544 processes block D′ forinclusion within backup copy 116 as is well known in the art, logic 544stores block-level backup copy 116 to backup media, e.g., disk/flash308, tape 309, and/or cloud service account 310. At step 8, logic 544populates backup block index 848 for the present backup copy 116 withstorage information about data block D′ and also adds cacheable flagsreceived from data agent 442 at step 6. At step 9, media agent 444(e.g., using logic 544) copies index 848 to backup media (e.g., 308,309, and/or 310). In some embodiments, index 848 is stored to the samebackup media as backup copy 116, because they are associated with eachother. Any data blocks that reach cache management logic 555 (e.g.,using step 6) are analyzed by logic 555 for whether they are flagged,and they are discarded if unflagged. As in FIG. 5 , data blocks D′received without a cacheable flag are not checked against index 556, asthey are not candidates for the live browse cache at this stage. Asdescribed in FIG. 5 in regard to steps 10, 11, and 12, data block D′ isadded to LBC 557 if not already therein and LBC index 556 is updatedaccordingly.

Steps 1-12 are included here to enhance the reader's understanding ofthe present disclosure, but the invention is not so limited. Otherembodiments implement different sequences of events and/or perform someof the depicted steps concurrently and/or include fewer or additionalsteps not shown here. Furthermore, data agent 442 and media agent 444are not limited to the functionality and data structures depicted in thepresent figure.

FIG. 9 depicts some salient operations of a method 900 according to anillustrative embodiment based on FIGS. 5-7 , in a scenario wherein thetype of source virtual machine/file system that comprises primary data112 is known to the originating data agent 442. In this configuration,data agent 442 recognizes certain key aspects of source file system 314or source VM disk 305 that are relevant to live browse cache management.Method 900 is performed by one or more components of system 300, such asdata backup and retrieval components 315, e.g., storage manager 440,data agent 442, media agent 444, and/or pseudo-disk driver 456.Additional details are given in FIGS. 5-7 . In the present figure, aswell as in FIGS. 10A and 10B, notations in square brackets [x] indicatedifferent versions of an element as the illustrative method progresses,e.g., a first version of live browse cache is referred to as LBC[1], anda later version is referred to as LBC[2], etc.

At block 902, method 900 executes a full block-level backup operation ofsource primary data 112 of a type that is known to originating dataagent 442. As shown in FIG. 5 , this results in a first block-levelbackup copy 116[1], and includes populating certain data blocks to livebrowse cache 557, expressed here as LBC[1], and further includes addingcacheable flags to backup block index 546, expressed here as Flags[1].Block 902 is followed by a first user-driven live browse operation atblock 904 or a first file indexing operation at block 906.

At block 904, method 900 performs a first user-driven live browse ofbackup copy 116[1], as described in FIG. 6 . This operation includesrecalling data blocks from LBC[1], i.e., the version of live browsecache 557 created during the full backup at block 902. Data blocks notfound in LBC[1] are recalled from backup copy 116[1] in backup media andthese blocks are added to live browse cache 557, resulting in LBC[2].Control passes to block 908 for another user-driven live browse, or toblock 906 for a file indexing operation.

At block 906, method 900 performs a file indexing operation of backupcopy 116[1], as described in FIG. 7 . This operation includes recallingdata blocks from live browse cache LBC[1], i.e., the version of livebrowse cache 557 created during the full backup at block 902. Datablocks not found in LBC[1] are recalled from backup copy 116[1] inbackup media and these blocks are added to live browse cache 557,resulting in LBC[2]. If block 906 follows block 904, some data blocksare recalled from LBC[2], which was updated at block 904.

At block 908, method 900 performs a user-driven live browse of backupcopy 116[1] that follows an earlier user-driven live browse at block 904or a file indexing operation at block 906. In other words, block 908continues to tap the current live browse cache 557, e.g., LBC[2], andadds additional data blocks recalled from backup copy 116[1] to formLBC[3].

At block 910, method 900 performs an incremental or a differentialbackup operation of the same source primary data 112 that was fullybacked up at block 902. Backup copy 116[2] is generated here and storedto backup media as shown in FIG. 5 . The originating data agent 442identifies changed data blocks in primary data 112 that are to be backedup to the incremental/differential backup copy 116[2]. Changed datablocks that are flagged as cacheable are added to live browse cache 557,resulting in LBC[4]. Backup block index 546 is generated for the presentbackup copy 116[2], and includes cacheable flags, e.g., Flags[2].Control passes to block 906 for file indexing of backup copy 116[2].Control passes to block 908 for user-driven live browsing of backup copy116[2].

At block 912, method 900 (e.g., cache management logic 555) prunes livebrowse cache 557, based on information in heat map 646. Accordingly,when certain storage thresholds are reached/exceeded by the amount ofdata stored in live browse cache 557, cache management logic 555 takesaction to prune data blocks from LBC 557 to make room for furtheradditions to the live browse cache. Illustratively, thresholds are setin cache management logic 555. For example, when live browse cache 557reaches a pruning threshold (e.g., 75%) of maximum allowed storagespace, pruning is invoked. Cache management logic 555 reviews usefrequencies in heat map 646 and selects least-used data blocks to deletefrom LBC 557. A sufficient number of least-used data blocks are deletedfrom LBC 557 to bring the storage metric below the pruning threshold. Insome embodiments, pruning is invoked based on elapsed time, e.g.,weekly. In some embodiments, least-used data blocks that were morerecently recalled than other similarly least-used data blocks areretained by the pruning logic, on the possibility that they are morelikely to be recalled again soon. These figures and implementationchoices are given here as examples, and the invention is not limitedthereby.

FIG. 10A depicts some salient operations of a method 1000 according toan illustrative embodiment based on FIGS. 8A, 8B, 6, and 7 , in ascenario wherein the type of source virtual machine/file system thatcomprises primary data 112 is unknown to the originating data agent 442.In this configuration, data agent 442 lacks the capacity to recognizecertain key aspects of source file system 314 or source VM disk 305 thatare relevant to live browse cache management. Method 1000 is performedby one or more components of system 300, such as data backup andretrieval components 315, e.g., storage manager 440, data agent 442,media agent 444, and/or pseudo-disk driver 456.

At block 1002, method 1000 executes a full backup operation of sourceprimary data 112 of a type that is unknown to originating data agent442. As shown in FIG. 8A, this results in a first block-level backupcopy 116[1]. Because a full backup does not rely on preceding backups,and because data agent 442 does not recognize whether any source datablocks are cacheable to the live browse cache, live browse cache 557 isnot populated by the present full backup operation, resulting in anempty LBC[1]. Likewise, no cacheable flags are added to backup blockindex 846, resulting in null Flags [1]. Block 1002 is followed by afirst user-driven live browse operation at block 1004 or a first fileindexing operation at block 1006.

At block 1004, method 1000 performs a first user-driven live browse ofbackup copy 116[1], as described in FIG. 6 . This operation recalls allneeded data blocks from backup copy 116[1] on backup media, because nodata blocks were populated to LBC[1] during the full backup operation.All data blocks recalled from backup copy 116[1] are added to LBC 557,resulting in LBC[2]. Thus, the present user-driven live browse operationdoes not benefit from the live browse cache (i.e., it experiencesrelatively slow performance as data blocks are retrieved from backupmedia), but by populating live browse cache 557, it causes futureoperations to benefit. Control passes to block 1008 for a subsequentuser-driven live browse operation.

At block 1006, method 1000 performs a first file indexing operation ofbackup copy 116[1], as described in FIG. 7 . Like the first-timeuser-driven live browse at block 1004, this operation recalls all neededdata blocks from backup copy 116[1] on backup media, because no datablocks were populated to LBC[1] during the full backup operation. Alldata blocks recalled from backup copy 116[1] are added to LBC 557,resulting in LBC[2]. Thus, the present file indexing operation does notbenefit from the live browse cache (i.e., it experiences relatively slowperformance as data blocks are retrieved from backup media), but bypopulating live browse cache 557, it causes future operations tobenefit. Control passes to block 1008 for a subsequent user-driven livebrowse operation.

At block 1008, method 1000 performs a user-driven live browse of backupcopy 116[1] that follows an earlier user-driven live browse at block1004 or a file indexing operation at block 1006. See also FIG. 6 .Because these earlier operations populated data blocks into live browsecache LBC[2], the present live browse preferentially recalls data blocksfrom LBC[2], and if not found there, recalls other data blocks frombackup copy 116[1] on backup media. All data blocks recalled from backupcopy 116[1] are added to LBC 557, resulting in LBC[3]. Thus, the presentuser-driven live browse realizes faster performance from using the livebrowse cache, and by further populating the live browse cache, it causesfuture operations to benefit as well. Control passes to block 1010.

At block 1010, method 1000 performs an incremental or a differentialbackup operation of the same source primary data 112 that was backed upat block 1002 as shown in FIG. 8B. Backup copy 116[2] is generated hereand stored to backup media. The originating data agent 442 lacks thecapacity, as it did in the full backup operation, to recognize cacheabledata blocks in the source primary data 112. However, data agent 442queries media agent 444 as to whether changed data blocks detected bydata agent 442 for the present incremental/differential operation have acorresponding (earlier version) in the live browse cache, e.g., LBC[3].Data agent 442 flags changed data blocks corresponding to those inLBC[3] and the changed data blocks are added to live browse cache 557,resulting in LBC[4]. Moreover, cacheable flags are added to backup blockindex 848, resulting in Flags[2]. At this point, live browse cache 557comprises data blocks that were browsed/used in earlier live browse/fileindexing operations, and further comprises any corresponding changeddata blocks backed up during the present incremental/differential backupoperation. Thus, even though data agent 442 lacks the capacity torecognize data blocks suitable for the live browse cache within primarydata 112, other techniques are used for populating the live browse cacheon a going-forward basis. These techniques also help to populatecacheable flags into backup block index 848 created with backup copy116[2].

At block 1012, method 1000 performs a file indexing operation of backupcopy 116[2] generated at block 1010, as shown in FIG. 7 . Becauseearlier operations populated data blocks into live browse cache LBC[4],the present file indexing operation preferentially recalls data blocksfrom LBC[4], and if not found there, recalls other data blocks frombackup copy 116[2] on backup media. All data blocks recalled from backupcopy 116[2] are added to LBC 557, resulting in LBC[5]. Thus, the presentoperation benefits from using the live browse cache, and by furtherpopulating the live browse cache, it causes future operations to benefitas well. Control passes to block 1014 in FIG. 10B.

FIG. 10B depicts some additional salient operations of method 1000.

At block 1014, which follows block 1012 in FIG. 10A, method 1000performs another full backup operation of the source primary data 112,resulting in block-level backup copy 116[3], as shown in FIG. 8A. As inblock 1002, this operation does not populate live browse cache 557 anddoes not add flags to backup block index 848.

At block 1016, method 1000 performs a file indexing operation ofblock-level backup copy 116[3] generated at block 1014. In contrast toblock 1006, block 1016 takes advantage of earlier operations to speed upthe present file indexing. Accordingly, media agent 444 uses thecacheable flags from an earlier backup, e.g., Flags[2] generated atblock 1010 as a guidepost to pre-fetching data blocks from backup media.Although data blocks flagged in an earlier backup operation are unlikelyto be a perfect match for the present backup copy 116[3], the presentoperation fetches them sequentially from backup media, which is fasterthan one-by-one on-demand fetches as requested by the media agent'soperating system. Data blocks that were not pre-fetched are then fetchedon demand as the file indexing operation progresses. All data blocksrecalled from backup copy 116[3] are added to the live browse cache,e.g., LBC[6], for future use. Control passes to block 1008 foruser-driven live browse or to block 1010 for another backup operation.

At block 1018, method 1000 (e.g., cache management logic 555 in mediaagent 444) prunes live browse cache 557, based on information in heatmap 646. This operation was described in more detail in block 912 ofFIG. 9 .

In regard to the figures described herein, other embodiments arepossible within the scope of the present invention, such that theabove-recited components, steps, blocks, operations, messages, requests,queries, and/or instructions are differently arranged, sequenced,sub-divided, organized, and/or combined. In some embodiments, adifferent component may initiate or execute a given operation. Forexample, in some embodiments, logic for managing the live browse cacheand storage for the live browse cache are configured outside the mediaagent, e.g., on an indexing server computing device. For example, insome embodiments, the media agent transmits the live browse cache indexand/or the backup block index (including the live browse cache flags) tothe data agent at the beginning of each backup job, thus enabling thedata agent to identify data blocks to flag for live browse caching.

Example Embodiments

Some example enumerated embodiments of the present invention are recitedin this section in the form of methods, systems, and non-transitorycomputer-readable media, without limitation.

In an exemplary embodiment, a computer-implemented method for populatinga cache storage area in a data storage management system, the methodcomprises: by a media agent at a first computing device, populating acache storage area at the media agent with data blocks read during afile indexing operation of a backup copy, wherein the backup copy wasgenerated in a block-level backup operation of primary data, and whereinthe populating comprises: by the media agent, receiving an indicationthat the file indexing operation has been initiated by a secondcomputing device, receiving a first read request issued by the fileindexing operation for a first data block of the backup copy, (i) if themedia agent determines that the first data block is in the cache storagearea, retrieving the first data block from the cache storage area, and(ii) if the media agent determines that the first data block is not inthe cache storage area, retrieving the first data block from the backupcopy stored on backup media, adding the first data block to the cachestorage area, and updating a cache-index to indicate that the first datablock is in the cache storage area; wherein the first data block andother data blocks added to the cache storage area during the fileindexing operation are available to be read from the cache storage areaand not from the backup copy for subsequent live browse operations ofthe backup copy; and wherein the first computing device comprises one ormore hardware processors and wherein the second computing devicecomprises one or more hardware processors.

The above-recited embodiment, wherein data blocks in the cache storagearea are available for retrieval therefrom in one or more of: subsequentlive browse operations of the backup copy, subsequent file indexingoperations of the backup copy, and subsequent file-level restores of thebackup copy, rather than being retrieved from the backup copy on backupmedia. The above-recited embodiment further comprising: by the mediaagent, receiving a second read request for the first data block of thebackup copy issued by a subsequent live browse operation of the backupcopy, and based on using the cache-index to determine that the firstdata block is in the cache storage area, retrieving the first data blockfrom the cache storage area and not from the backup copy. Theabove-recited embodiment further comprising: by the media agent during asubsequent incremental block-level backup operation of the primary data:identifying that a changed version of the first data block is beingbacked up to a second backup copy, based on using the cache-index,determining that the first data block is in the cache storage area,adding the changed version of the first data block to the cache storagearea, and updating the cache-index to indicate that the changed versionof the first data block is in the cache storage area; and wherein in alive browse operation of the second backup copy, the changed version ofthe first data block is retrieved from the cache storage area and notfrom the second backup copy. The above-recited embodiment furthercomprising during the subsequent incremental block-level backupoperation that generates the second backup copy: in a backup-index thattracks where data blocks are stored on backup media, flagging thechanged version of the first data block as a data block suitable for thecache storage area; and wherein flags in the backup-index are used in asubsequent file indexing operation of a third backup copy of the primarydata to pre-fetch from the third backup copy second data blockscorresponding to data blocks of the second backup copy flagged assuitable for the cache storage area, including the first data block, andwherein the pre-fetch is performed in a sequential order according towhere the second data blocks are stored on the backup media. Theabove-recited embodiment wherein the pre-fetch enables the subsequentfile indexing operation of the third backup copy to complete sooner ascompared to on demand serving read requests issued by the subsequentfile indexing operation. The above-recited embodiment further comprisingduring the subsequent incremental block-level backup operation thatgenerates the second backup copy: in a backup-index that tracks wheredata blocks are stored on backup media, flagging the changed version ofthe first data block as a data block suitable for the cache storagearea; and wherein flags in the backup-index are used instead of thecache-index in a subsequent live browse operation of the second backupcopy to determine whether to add a given data block of the second backupcopy to the cache storage area for later retrieval therefrom instead offrom the backup media. The above-recited embodiment wherein a virtualmachine generates the primary data, which resides on a virtual disk. Theabove-recited embodiment wherein a virtual machine generates the primarydata, which resides in a cloud storage environment. The above-recitedembodiment wherein one or more applications that execute on a thirdcomputing device, distinct from the first computing device, generate theprimary data. The above-recited embodiment wherein the first backup copyis stored to one or more a cloud storage environments. The above-reciteembodiment wherein the first backup copy is stored to magnetic tape.

According to another exemplary embodiments, a computer-implementedmethod for populating a cache storage area in a data storage managementsystem, the method comprises: by a media agent, populating a cachestorage area with data blocks read during a first live browse operationof a backup copy, wherein the backup copy was generated in a block-levelbackup operation of primary data, and wherein the populating comprises:by the media agent, receiving a first read request issued by the firstlive browse operation for a first data block of the backup copy, and (i)if the media agent determines that the first data block is in the cachestorage area, retrieving the first data block from the cache storagearea, and (ii) if the media agent determines that the first data blockis not in the cache storage area, retrieving the first data block fromthe backup copy, adding the first data block to the cache storage area,and updating a cache-index to indicate that the first data block is inthe cache storage area; by the media agent during a subsequentincremental block-level backup operation of the primary data:identifying that a changed version of the first data block is beingbacked up to a second backup copy, determining that the first data blockis in the cache storage area, in a backup-index that tracks where datablocks are stored on backup media, flagging the changed version of thefirst data block as a data block suitable for the cache storage area,adding the changed version of the first data block to the cache storagearea, and updating the cache-index to indicate that the changed versionof the first data block is in the cache storage area.

The above-recited embodiment, wherein data blocks in the cache storagearea are available for retrieval therefrom in one or more of: subsequentlive browse operations of the backup copy, subsequent file indexingoperations of the backup copy, and subsequent file-level restores of thebackup copy, rather than being retrieved from the backup copy on backupmedia. The above-recited embodiment wherein in a subsequent fileindexing operation of the second backup copy, the changed version of thefirst data block is retrieved from the cache storage area and not fromthe second backup copy on the backup media; and wherein the media agentexecutes on a first computing device comprising one or more hardwareprocessors. The above-recited embodiment wherein a data agent associatedwith the primary data indicates to the media agent that the changedversion of the first data block is being backed up to the second backupcopy. The above-recited embodiment further comprising: by the mediaagent, storing a third backup copy of the primary data to backup media,wherein the third backup copy is generated by a full block-level backupoperation. The above-recited embodiment further comprising: in a fileindexing operation of the third backup copy: identifying one or moredata blocks of the third backup copy that are flagged in thebackup-index as suitable for the cache storage area, defining asequential order for the one or more data blocks of the third backupcopy according to where they are stored on the backup media,sequentially retrieving the one or more data blocks from the backupmedia according to the sequential order, adding the one or more datablocks to the cache storage area, updating the cache-index to indicatethat the one or more data blocks of the third backup copy are in thecache storage area, serving read requests issued by the file indexingoperation of the third backup copy for the one or more data blocks fromthe cache storage area, and retrieving on demand other data blocksneeded for the file indexing operation of the third backup copy from thebackup media to serve read requests issued by the file indexingoperation for the other data blocks; wherein the sequentiallyretrieving, adding, and serving of the one or more data blocks from thecache storage area is faster than on demand retrieving the one or moredata blocks from the third backup copy on the backup media to serve theread requests issued by the file indexing operation for the one or moredata blocks. The above-recited embodiment wherein the backup media ispart of a cloud storage environment. The above-recited embodimentwherein the backup media comprises magnetic tape. The above-recitedembodiment wherein a virtual machine generates the primary data, whichresides on a virtual disk. The above-recited embodiment wherein avirtual machine generates the primary data, which resides in a cloudstorage environment. The above-recited embodiment wherein one or moreapplications that execute on a second computing device distinct from thefirst computing device generate the primary data. The above-recitedembodiment wherein a pseudo-disk driver is interposed between a secondcomputing device that initiates the first live browse operation and themedia agent, and wherein the first data block is transmitted by themedia agent to the pseudo-disk driver in response to an indication thatthe second computing device initiated the first live browse operation,and wherein the pseudo-disk driver responds to read requests of thefirst live browse operation issued by the second computing device; andwherein the pseudo-disk driver executes on one of: the first computingdevice that hosts the media agent, the second computing device thatinitiates the first live browse operation, and a third computing devicedistinct from the first and the second computing devices. Theabove-recited embodiment wherein the pseudo-disk driver serves readrequests of the first live browse operation from a first storage areathat comprises data blocks received from the media agent, including thefirst data block, and wherein the pseudo-disk driver stores data blocksfrom write operations issued by the first live browse operation to asecond storage area whose contents are discarded after the secondcomputing device terminates the first live browse operation. Theabove-recited method further comprising: by the media agent, receiving asecond read request for the first data block of the backup copy issuedby a second live browse operation of the backup copy, and based on usingthe cache-index to determine that the first data block is in the cachestorage area, retrieving the first data block therefrom not from thebackup copy.

According to yet another exemplary embodiment, a system comprising afirst computing device that executes a media agent and comprises a cachestorage area; wherein the first computing device is configured to:populating a cache storage area at the media agent with data blocks readduring a file indexing operation of a backup copy, wherein the backupcopy was generated in a block-level backup operation of primary data,and wherein the populating comprises: receiving an indication that thefile indexing operation has been initiated by a second computing device,receiving a first read request issued by the file indexing operation fora first data block of the backup copy, (i) if the first data block is inthe cache storage area, retrieving the first data block from the cachestorage area, and (ii) if the first data block is not in the cachestorage area, retrieving the first data block from the backup copystored on backup media, adding the first data block to the cache storagearea, and updating a cache-index to indicate that the first data blockis in the cache storage area; wherein the first data block and otherdata blocks added to the cache storage area during the file indexingoperation are available to be read from the cache storage area and notfrom the backup copy for subsequent live browse operations of the backupcopy; receiving a second read request for the first data block of thebackup copy issued by a subsequent live browse operation of the backupcopy, and based on using the cache-index to determine that the firstdata block is in the cache storage area, retrieving the first data blockfrom the cache storage area and not from the backup copy; and whereinthe first computing device comprises one or more hardware processors andwherein the second computing device comprises one or more hardwareprocessors. The above-recited embodiment further comprising a storagemanager that initiates the block-level backup operation of the primarydata. The above-recited embodiment further comprising a data agentassociated with the primary data. The above-recited embodiment whereinthe data agent indicates to the media agent that certain data blocksbeing backed up to the backup copy should be added to the cache storagearea. The above-recited embodiment wherein the data agent indicates tothe media agent that certain data blocks being backed up to the backupcopy are suitable to be added to the cache storage area. Theabove-recited embodiment wherein the data agent indicates to the mediaagent that certain data blocks being backed up to the backup copy shouldbe flagged in the backup-index as suitable to be added to the cachestorage area. The above-recited embodiment, wherein data blocks in thecache storage area are available for retrieval therefrom in one or moreof: subsequent live browse operations of the backup copy, subsequentfile indexing operations of the backup copy, and subsequent file-levelrestores of the backup copy, rather than being retrieved from the backupcopy on backup media.

According to an illustrative embodiment, a system comprises: a firstcomputing device, comprising one or more hardware processors, whichhosts a data agent associated with primary data, wherein the primarydata has been backed up to a backup copy using a block-level backupoperation; a second computing device, comprising one or more hardwareprocessors, which hosts a media agent, a first index that tracks wheredata blocks of the backup copy are stored on backup media, a cachestorage area managed by the media agent, and a second index that trackswhich data blocks are stored in the cache storage area; wherein thefirst computing device is configured to: during the block-level backupoperation, if the data agent recognizes a type of file system that hoststhe primary data, indicate to the media agent which data blocks beingbacked up to the backup copy are cacheable data blocks suitable to storeto the cache storage area; wherein the second computing device isconfigured to: store to the cache storage area certain data blocks ofthe backup copy, including the cacheable data blocks, during one or moreof: generating the backup copy, live browsing the backup copy, and fileindexing the backup copy and update the second index to indicate thecertain data blocks in the cache storage area; indicate in the firstindex which data blocks of the backup copy are the cacheable data blocksas indicated by the data agent, and store the backup copy to backupmedia; and wherein data blocks in the cache storage area are availableto be read from the cache storage area and not from the backup copy inone or more of: subsequent live browse operations of the backup copy,and subsequent file indexing operations of the backup copy.

The above-recited embodiment, wherein data blocks in the cache storagearea are available for retrieval therefrom in one or more of: subsequentlive browse operations of the backup copy, subsequent file indexingoperations of the backup copy, and subsequent file-level restores of thebackup copy, rather than being retrieved from the backup copy on backupmedia. The above-recited embodiment wherein at least some of thecacheable data blocks are descriptor block of the file system that hoststhe primary data. The above-recited embodiment wherein the secondcomputing device is further configured to: receive an indication that athird computing device initiated a subsequent live browse operation ofthe backup copy, wherein the third computing device comprises one ormore hardware processors; retrieve from the cache storage area firstdata blocks of the backup copy that are stored in the cache storagearea, if any, as indicated by the second index; retrieve from the backupcopy second data blocks of the backup copy that are needed to launch thesubsequent live browse operation and are not found in the cache storagearea, by using a sequential order of retrieval based on where the seconddata blocks are stored on the backup media as indicated by the firstindex; transmit the first and second data blocks in response to theindication that the third computing device initiated the subsequent livebrowse operation; issue a release command that allows the thirdcomputing device to accept user requests to live browse the backup copy;and store to the cache storage area third data blocks retrieved ondemand from the backup copy during the subsequent live browse operationif the third data blocks are not already in the cache storage area. Theabove-recited embodiment wherein the media agent is further configuredto, during the subsequent live browse operation: receive a read requestissued by the third computing device for a given data block of thebackup copy; if the second index indicates that the given data block isin the cache storage area, retrieve the given data block from the cachestorage area and not from the backup copy on the backup media, andtransmit the given data block in response to the read request. Theabove-recited embodiment wherein the media agent is further configuredto: if the given data block is not in the cache storage area, use thefirst index to determine where the given data block is stored on thebackup media and retrieve the given data block therefrom; transmit thegiven data block retrieved from the backup media in response to the readrequest and store the given data block to the cache storage area forretrieval in a subsequent one of: a live browse operation and a fileindexing operation. The above-recited embodiment wherein the media agentis further configured to: receive an indication that a third computingdevice initiated the subsequent file indexing operation of the backupcopy, wherein the third computing device comprises one or more hardwareprocessors; mount the backup copy to a mount point at the media agent;use the first index to identify the first data blocks in the backupcopy; retrieve from the cache storage area first data blocks of thebackup copy stored in the cache storage area as indicated by the secondindex; retrieve from the backup copy second data blocks needed for thefile indexing operation and not found in the cache storage area, byusing a sequential order of retrieval based on where these second datablocks are stored on the backup media as indicated by the first index;transmit the first and second data blocks in response to the indicationthat the third computing device initiated the subsequent file indexingoperation; and store to the cache storage area the second data blocksretrieved from the backup copy during the subsequent file indexingoperation if the second data blocks are not already in the cache storagearea.

The above-recited embodiment wherein the media agent is furtherconfigured to, during the subsequent file indexing operation: receive aread request issued by the third computing device for a third data blockof the backup copy; if the second index indicates that the third datablock is in the cache storage area, retrieve the third data block fromthe cache storage area; and transmit the third data block in response tothe read request without accessing the backup copy on the backup media.The above-recited embodiment wherein the media agent is furtherconfigured to: if the third data block is not in the cache storage area,use the first index to determine where the third data block is stored onthe backup media and retrieve the third data block therefrom; transmitthe third data block retrieved from the backup media in response to theread request and store the third data block to the cache storage areafor retrieval in a subsequent one of: a live browse operation and a fileindexing operation.

According to another illustrative embodiment, a computer-implementedmethod for managing a cache storage area in a data storage managementsystem, comprises: in the data storage management system, performing ablock-level backup operation that generates: a backup copy of primarydata that resides in a file system, and a first index that tracks wheredata blocks of the backup copy are stored on backup media, wherein thefirst index indicates that certain data blocks are file systemdescriptor blocks; by the media agent, using a second index stored atthe media agent to determine whether each of the file system descriptorblocks is stored in a cache storage area at the media agent, wherein themedia agent maintains the second index; if the media agent determinesthat a file descriptor block is not stored in the cache storage area,storing the file descriptor block to the cache storage area and updatingthe second index to so indicate; receiving an indication at the mediaagent that a computing device initiated a live browse operation inreference to the backup copy; by the media agent, using the first indexto identify data blocks in the backup copy that are file systemdescriptor blocks; if the media agent determines that first file systemdescriptor blocks of the backup copy are stored in the cache storagearea, retrieving the first file system descriptor blocks therefrom; ifthe media agent determines that second file system descriptor blocks ofthe backup copy are not stored in the cache storage area, using thefirst index to determine where the second file system descriptor blocksare stored on the backup media, defining a sequential order for thesecond file system descriptor blocks according to where they are storedon the backup media and sequentially retrieving them from the backupmedia according to the sequential order, wherein the backup copy ismounted to a mount point at the media agent; and storing the second filesystem descriptor blocks to the cache storage area and updating thesecond index to so indicate; transmitting one or more of: the first andsecond file system descriptor blocks of the backup copy in response tothe indication that the computing device initiated the live browseoperation; and issuing a release command that allows the computingdevice to accept user requests to live browse contents of the backupcopy.

The above-recited embodiment, wherein data blocks in the cache storagearea are available for retrieval therefrom in one or more of: subsequentlive browse operations of the backup copy, subsequent file indexingoperations of the backup copy, and subsequent file-level restores of thebackup copy, rather than being retrieved from the backup copy on backupmedia. The above-recited embodiment wherein the transmitting of the oneor more of the first and second file system descriptor blocks for thebackup copy before issuing the release command enables faster responsetimes of the live browse of the backup copy as compared to on demandserving read requests issued by the live browse operation for datablocks of the backup copy. The above-recited embodiment furthercomprising performing the live browse operation in the data storagemanagement system wherein data blocks from the backup copy that areretrieved in the live browse operation are added to the cache storagearea at the media agent. The above-recited embodiment wherein datablocks from the backup copy that are retrieved in the live browseoperation are added to the cache storage area at the media agent and areavailable therefrom for subsequent file indexing of the backup copy. Theabove-recited embodiment further comprising performing the live browseoperation in the data storage management system comprising: receiving,at the media agent, a read request issued by the computing device for afirst data object that was backed up to the backup copy, wherein thefirst data object comprises a first data block; by the media agent,using the second index to determine whether the first data block isstored in the cache storage area; if the media agent determines that thefirst data block is stored in the cache storage area, retrieving thefirst data block therefrom; if the media agent determines that the firstdata block is not stored in the cache storage area, using the firstindex to determine where the first data block is stored on the backupmedia, and retrieving the first data block from the backup media; andtransmitting the first data block in response to the read request. Theabove-recited embodiment wherein a pseudo-disk driver is interposedbetween the computing device that initiates the live browse operationand the media agent, and wherein the one or more of the first and secondfile system descriptor blocks for the backup copy are transmitted by themedia agent to the pseudo-disk driver in response to the indication thatthe computing device initiated the live browse operation, and whereinthe pseudo-disk driver responds to read requests of the live browseoperation issued by the computing device. The above-recited embodimentwherein the pseudo-disk driver responds to the read requests of the livebrowse operation from a first storage area that comprises data blocksreceived from the media agent, including the one or more of the firstand second file system descriptor blocks, and wherein data blocks fromwrite operations issued by the live browse operation are written to asecond storage area whose contents are discarded after the computingdevice terminates the live browse operation. The above-recitedembodiment wherein the block-level backup operation is one of a fullbackup, a differential backup, and an incremental backup. Theabove-recited embodiment wherein the file system descriptor blocks aredata blocks that are used in live browse operations. The above-recitedembodiment wherein the live browse operation uses file system descriptorblocks added to the cache storage area by the block-level backupoperation. The above-recited embodiment further comprising: receiving anindication at the media agent that a file indexing operation has beeninitiated in reference to the backup copy; by the media agent, using thefirst index to identify data blocks in the backup copy that are filesystem descriptor blocks; if the media agent determines that third filesystem descriptor blocks of the backup copy are stored in the cachestorage area, retrieving the third file system descriptor blockstherefrom; if the media agent determines that fourth file systemdescriptor blocks of the backup copy are not stored in the cache storagearea, using the first index to determine where the fourth file systemdescriptor blocks are stored on the backup media, defining a sequentialorder for the fourth file system descriptor blocks according to wherethey are stored on the backup media and sequentially retrieving themfrom the backup media according to the sequential order, storing thefourth file system descriptor blocks to the cache storage area andupdating the second index to so indicate; transmitting one or more ofthe third and fourth file system descriptor blocks of the backup copy inresponse to the indication that the file indexing operation has beeninitiated; and generating a file index of the backup copy, based on thefile system descriptor blocks obtained from the media agent, includingthe one or more of the third and fourth file system descriptor blocks,wherein the file index indicates what data objects are backed up in thebackup copy. The above-recited embodiment wherein the primary data isgenerated by one or more applications that store the primary data in thefile system to one or more primary data storage devices. Theabove-recited embodiment wherein the primary data is generated by avirtual machine that stores the primary data to a virtual disk.

According to yet another illustrative embodiment, a computer-implementedmethod for managing a cache storage area in a data storage managementsystem, the method comprises: in the data storage management system,performing a block-level backup operation that generates: a backup copyof primary data that resides in a file system, and a first index thattracks where data blocks of the backup copy are stored on backup media;by the media agent, using a second index to determine whether each ofthe file system descriptor blocks is stored in a cache storage area atthe media agent, wherein the media agent maintains the second index andthe cache storage area, and wherein the media agent executes on a firstcomputing device comprising one or more hardware processors; if a filedescriptor block is not stored in the cache storage area, storing thefile descriptor block to the cache storage area and updating the secondindex to so indicate; performing a live browse operation at a secondcomputing device in the data storage management system comprising:receiving, at the media agent, a read request issued by the computingdevice for a first data block that was backed up to the backup copy, if,according to the second index, the first data block is stored in thecache storage area, retrieving the first data block therefrom, if thefirst data block is not in the cache storage area, using the first indexto determine where the first data block is stored on the backup media,and retrieving the first data block therefrom, wherein the backup copyis mounted to a mount point at the first computing device; transmittingthe first data block in response to the read request.

The above-recited embodiment, wherein data blocks in the cache storagearea are available for retrieval therefrom in one or more of: subsequentlive browse operations of the backup copy, subsequent file indexingoperations of the backup copy, and subsequent file-level restores of thebackup copy, rather than being retrieved from the backup copy on backupmedia. The above-recited embodiment wherein, before receiving the readrequest the method further comprises: receiving an indication at themedia agent that the second computing device initiated the live browseoperation in reference to the backup copy; mounting the backup copy tothe mount point at the first computing device; by the media agent, usingthe first index to identify data blocks in the backup copy that are filesystem descriptor blocks; if first file system descriptor blocks arestored in the cache storage area, retrieving the first file systemdescriptor blocks therefrom; if second file system descriptor blocks arenot stored in the cache storage area, using the first index to determinewhere the second file system descriptor blocks are stored on the backupmedia, defining a sequential order for the second file system descriptorblocks according to where they are stored on the backup media andsequentially retrieving them from the backup media according to thesequential order, storing the second file system descriptor blocks tothe cache storage area and updating the second index to so indicate;transmitting one or more of the first and second file system descriptorblocks of the backup copy in response to the indication that the secondcomputing device initiated the live browse operation; and issuing arelease command that allows the computing device to accept user input tolive browse contents of the backup copy, including a user input thatcomprises the read request for the first data block of the backup copy.The above-recited embodiment wherein, before receiving the read requestthe method further comprises: receiving an indication at the media agentthat the second computing device initiated the live browse operation inreference to the backup copy, wherein the second computing device iscommunicatively coupled with a pseudo-disk driver that is interposedbetween the second computing device and the media agent; mounting thebackup copy to a mount point at the first computing device; by the mediaagent, using the first index to identify data blocks in the backup copythat are file system descriptor blocks; if the media agent determinesthat first file system descriptor blocks are stored in the cache storagearea, retrieving the first file system descriptor blocks therefrom; ifthe media agent determines that second file system descriptor blocks arenot stored in the cache storage area, using the first index to determinewhere the second file system descriptor blocks are stored on the backupmedia, defining a sequential order for the second file system descriptorblocks according to where they are stored on the backup media andsequentially retrieving them from the backup media according to thesequential order, storing the second file system descriptor blocks tothe cache storage area and updating the second index to so indicate;transmitting one or more of the first and second file system descriptorblocks for the backup copy to the pseudo-disk driver; issuing a releasecommand that allows the computing device to accept user requests to livebrowse contents of the backup copy, including a user request thatcomprises the read request for the first data block of the backup copy;and wherein the pseudo-disk driver responds to read requests of the livebrowse operation, including the read request for the first data block,from a first storage area that comprises data blocks received from themedia agent, including the one or more of the first and second filesystem descriptor blocks, and wherein data blocks from write operationsissued by the live browse operation are written to a second storage areawhose contents are discarded after the computing device terminates thelive browse operation.

The above-recited embodiment wherein the file system descriptor blocksfor the backup copy are transmitted by the media agent to thepseudo-disk driver in response to the indication that the computingdevice initiated the live browse operation, and wherein the pseudo-diskdriver responds to read requests of the live browse operation issued bythe computing device. The above-recited embodiment wherein thepseudo-disk driver serves read requests of live browse operations from afirst storage area that comprises data blocks received from the mediaagent, and wherein data blocks from write operations issued by the livebrowse operation are written to a second storage area whose contents arediscarded after the computing device terminates the live browseoperation. The above-recited embodiment wherein the media agent executeson a first computing device comprising one or more hardware processors,and wherein the pseudo-disk driver executes on one of: the firstcomputing device and a second computing device comprising one or morehardware processors and which is communicatively coupled to the firstcomputing device. The above-recited embodiment wherein the file systemdescriptor blocks are associated with the file system. The above-recitedembodiment wherein a virtual machine generates the primary data, whichis stored in a virtual disk in the file system, and wherein the filesystem descriptor blocks are associated with the file system. Theabove-recited embodiment further comprising: by a data agent componentof the data storage management system, indicating to the media agentduring the block-level backup operation, that a data block being backedup to the backup copy is a type of data block to be added to the cachestorage area, and wherein a file system descriptor block is of the typeof data block to be added to the cache storage area. The above-recitedembodiment further comprising: by a data agent component of the datastorage management system, indicating to the media agent that a datablock being backed up to the backup copy is a type of data block to beadded to the cache storage area, and wherein a file system descriptorblock is of the type of data block to be added to the cache storagearea. The above-recited embodiment wherein the data agent is specific tothe file system. The above-recited embodiment wherein the data agent isa virtual server data agent associated with a computing device thathosts a virtual machine that generates the primary data. Theabove-recited embodiment further comprising: by a data agent componentof the data storage management system, indicating to the media agentthat a data block being backed up to the backup copy is a file systemdescriptor block. The above-recited embodiment wherein using the secondindex by the media agent to determine whether each of the file systemdescriptor blocks is stored in the cache storage area is based on thedata agent indicating that a data block being backed up to the backupcopy is a file system descriptor block. The above-recited embodimentwherein the data agent is specific to the file system. The above-recitedembodiment wherein the data agent is a virtual server data agentassociated with a computing device that hosts a virtual machine thatgenerates the primary data. The above-recited embodiment wherein theprimary data in the file system is generated by one or more applicationsthat execute on a computing device. The above-recited embodiment whereinthe primary data is generated by one or more virtual machines thatexecute on a computing device, and wherein a virtual disk associatedwith the one or more virtual machines comprises the primary data. Theabove-recited embodiment further comprising: if the media agentdetermines that the first data block is not stored in the cache storagearea, storing the first data block to the cache storage area andupdating the second index to so indicate. The above-recited embodimentfurther comprising: populating a data structure at the media agent thattracks each retrieval of each data block, whether retrieved from thecache storage area or from the backup copy on backup media. Theabove-recited embodiment further comprising: populating a data structureat the media agent that tracks each retrieval of each data block,whether retrieved from the cache storage area or from the backup copy onbackup media; and pruning data blocks from the cache storage area basedon retrieval information in the data structure. The above-recitedembodiment wherein the media agent executes on a first computing devicecomprising one or more hardware processors, and wherein the firstcomputing device is distinct from the computing device that performs thelive browse operation. The above-recited embodiment wherein the mediaagent executes on a first computing device comprising one or morehardware processors; wherein the file system descriptor blocks areassociated with the file system of the primary data; and wherein a dataagent component of the data storage management system, which isassociated with the primary data, indicates to the media agent that adata block being backed up to the backup copy is a file systemdescriptor block, wherein the data agent executes on one of: the firstcomputing device, and a second computing device comprising one or morehardware processors and which is communicatively coupled to the primarydata. The above-recited embodiment wherein the block-level backupoperation is managed by a storage manager that executes on a firstcomputing device comprising one or more hardware processors; wherein themedia agent executes on a second computing device comprising one or morehardware processors; and wherein the backup copy is generated underinstructions received by the media agent from the storage manager.

According to yet one more illustrative embodiment, acomputer-implemented method for managing a cache storage area for fileindexing operations in a data storage management system, the methodcomprises: in the data storage management system, performing ablock-level backup operation that generates: a backup copy of primarydata that resides in a file system, and a first index that tracks wheredata blocks of the backup copy are stored on backup media, wherein thefirst index is generated and maintained by a media agent component ofthe data storage management system, wherein the first index indicatesthat certain data blocks are file system descriptor blocks; by the mediaagent, using a second index stored at the media agent to determinewhether each of the file system descriptor blocks is stored in a cachestorage area at the media agent, wherein the media agent maintains thesecond index and the cache storage area; if the media agent determinesthat a file descriptor block is not stored in the cache storage area,storing the file descriptor block to the cache storage area and updatingthe second index to so indicate; receiving an indication at the mediaagent that a file indexing operation has been initiated in reference tothe backup copy; mounting the backup copy to a mount point at the mediaagent; by the media agent, using the first index to identify all datablocks in the backup copy that are file system descriptor blocks; if themedia agent determines that first file system descriptor blocks of thebackup copy are stored in the cache storage area, retrieving the firstfile system descriptor blocks therefrom; if the media agent determinesthat second file system descriptor blocks of the backup copy are notstored in the cache storage area, using the first index to determinewhere the second file system descriptor blocks are stored on the backupmedia, defining a sequential order for the second file system descriptorblocks according to where they are stored on the backup media andsequentially retrieving them from the backup media according to thesequential order, storing the second file system descriptor blocks tothe cache storage area and updating the second index to so indicate;transmitting all the file system descriptor blocks for the backup copyin response to the indication that the file indexing operation has beeninitiated; and generating a file index of the backup copy, based on thefile system descriptor blocks obtained from the media agent, wherein thefile index indicates what data file objects are backed up in the backupcopy.

The above-recited embodiment, wherein data blocks in the cache storagearea are available for retrieval therefrom in one or more of: subsequentlive browse operations of the backup copy, subsequent file indexingoperations of the backup copy, and subsequent file-level restores of thebackup copy, rather than being retrieved from the backup copy on backupmedia. The above-recited embodiment wherein the media agent generatesthe file index. The above-recited embodiment wherein an indexing serverdistinct from a computing device that hosts the media agent generatesthe file index. The above-recited embodiment further comprisingperforming a live browse operation of the backup copy after thegenerating of the file index of the backup copy, comprising: receiving,at the media agent, a read request issued by a computing device for afirst data object that was backed up to the backup copy, wherein thefirst data object comprises a first data block; by the media agent,using the second index to determine whether the first data block isstored in the cache storage area; if the media agent determines that thefirst data block is stored in the cache storage area, retrieving thefirst data block therefrom; if the media agent determines that the firstdata block is not stored in the cache storage area, using the firstindex to determine where the data block is stored on the backup media,and retrieving the first data block from the backup media; andtransmitting the first data block in response to the read request. Theabove-recited embodiment wherein a pseudo-disk driver is interposedbetween the computing device that initiates the live browse operationand the media agent, and wherein file system descriptor blocks for thebackup copy are transmitted by the media agent to the pseudo-disk driverin response to the indication that the computing device initiated thelive browse operation, and wherein the pseudo-disk driver responds toread requests of the live browse operation issued by the computingdevice. The above-recited embodiment wherein the pseudo-disk driverserves read requests of the live browse operations from a first storagearea that comprises data blocks received from the media agent, andwherein data blocks from write operations issued by the live browseoperation are written to a second storage area whose contents arediscarded after the computing device terminates the live browseoperation. The above-recited embodiment wherein a pseudo-disk driver isinterposed between a computing device that generates the file index andthe media agent, and wherein file system descriptor blocks for thebackup copy are transmitted by the media agent to the pseudo-disk driverin response to the indication that the file indexing operation has beeninitiated, and wherein the pseudo-disk driver responds to read requestsof the file indexing operation issued by the computing device thatgenerates the file index. The above-recited embodiment wherein thepseudo-disk driver serves read requests of the indexing operation from afirst storage area that comprises data blocks received from the mediaagent, and wherein data blocks from write operations issued by the fileindexing operation are written to a second storage area whose contentsare discarded after the file indexing operation ends. The above-recitedembodiment wherein data blocks from the backup copy that are used in thefile indexing operation are added to the cache storage area at the mediaagent. The above-recited embodiment wherein data blocks from the backupcopy that are used in the file indexing operation are added to the cachestorage area at the media agent and are available therefrom forsubsequent live browse operations of the backup copy.

***

In other embodiments according to the present invention, a system orsystems operates according to one or more of the methods and/orcomputer-readable media recited in the preceding paragraphs. In yetother embodiments, a method or methods operates according to one or moreof the systems and/or computer-readable media recited in the precedingparagraphs. In yet more embodiments, a non-transitory computer-readablemedium or media causes one or more computing devices having one or moreprocessors and computer-readable memory to operate according to one ormore of the systems and/or methods recited in the preceding paragraphs.

Terminology

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense, i.e., in the sense of “including, but notlimited to.” As used herein, the terms “connected,” “coupled,” or anyvariant thereof means any connection or coupling, either direct orindirect, between two or more elements; the coupling or connectionbetween the elements can be physical, logical, or a combination thereof.Additionally, the words “herein,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. Where thecontext permits, words using the singular or plural number may alsoinclude the plural or singular number respectively. The word “or” inreference to a list of two or more items, covers all of the followinginterpretations of the word: any one of the items in the list, all ofthe items in the list, and any combination of the items in the list.Likewise, the term “and/or” in reference to a list of two or more items,covers all of the following interpretations of the word: any one of theitems in the list, all of the items in the list, and any combination ofthe items in the list.

In some embodiments, certain operations, acts, events, or functions ofany of the algorithms described herein can be performed in a differentsequence, can be added, merged, or left out altogether (e.g., not allare necessary for the practice of the algorithms). In certainembodiments, operations, acts, functions, or events can be performedconcurrently, e.g., through multi-threaded processing, interruptprocessing, or multiple processors or processor cores or on otherparallel architectures, rather than sequentially.

Systems and modules described herein may comprise software, firmware,hardware, or any combination(s) of software, firmware, or hardwaresuitable for the purposes described. Software and other modules mayreside and execute on servers, workstations, personal computers,computerized tablets, PDAs, and other computing devices suitable for thepurposes described herein. Software and other modules may be accessiblevia local computer memory, via a network, via a browser, or via othermeans suitable for the purposes described herein. Data structuresdescribed herein may comprise computer files, variables, programmingarrays, programming structures, or any electronic information storageschemes or methods, or any combinations thereof, suitable for thepurposes described herein. User interface elements described herein maycomprise elements from graphical user interfaces, interactive voiceresponse, command line interfaces, and other suitable interfaces.

Further, processing of the various components of the illustrated systemscan be distributed across multiple machines, networks, and othercomputing resources. Two or more components of a system can be combinedinto fewer components. Various components of the illustrated systems canbe implemented in one or more virtual machines, rather than in dedicatedcomputer hardware systems and/or computing devices. Likewise, the datarepositories shown can represent physical and/or logical data storage,including, e.g., storage area networks or other distributed storagesystems. Moreover, in some embodiments the connections between thecomponents shown represent possible paths of data flow, rather thanactual connections between hardware. While some examples of possibleconnections are shown, any of the subset of the components shown cancommunicate with any other subset of components in variousimplementations.

Embodiments are also described above with reference to flow chartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products. Each block of the flow chart illustrationsand/or block diagrams, and combinations of blocks in the flow chartillustrations and/or block diagrams, may be implemented by computerprogram instructions. Such instructions may be provided to a processorof a general purpose computer, special purpose computer,specially-equipped computer (e.g., comprising a high-performancedatabase server, a graphics subsystem, etc.) or other programmable dataprocessing apparatus to produce a machine, such that the instructions,which execute via the processor(s) of the computer or other programmabledata processing apparatus, create means for implementing the actsspecified in the flow chart and/or block diagram block or blocks. Thesecomputer program instructions may also be stored in a non-transitorycomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to operate in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the acts specified in the flow chart and/or blockdiagram block or blocks. The computer program instructions may also beloaded to a computing device or other programmable data processingapparatus to cause operations to be performed on the computing device orother programmable apparatus to produce a computer implemented processsuch that the instructions which execute on the computing device orother programmable apparatus provide steps for implementing the actsspecified in the flow chart and/or block diagram block or blocks.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the invention can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further implementations of theinvention. These and other changes can be made to the invention in lightof the above Detailed Description. While the above description describescertain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention under theclaims.

To reduce the number of claims, certain aspects of the invention arepresented below in certain claim forms, but the applicant contemplatesother aspects of the invention in any number of claim forms. Forexample, while only one aspect of the invention is recited as ameans-plus-function claim under 35 U.S.C sec. 112(f) (AIA), otheraspects may likewise be embodied as a means-plus-function claim, or inother forms, such as being embodied in a computer-readable medium. Anyclaims intended to be treated under 35 U.S.C. § 112(f) will begin withthe words “means for,” but use of the term “for” in any other context isnot intended to invoke treatment under 35 U.S.C. § 112(f). Accordingly,the applicant reserves the right to pursue additional claims afterfiling this application, in either this application or in a continuingapplication.

What is claimed is:
 1. A computer-implemented method for populating acache storage area in a data storage management system, the methodcomprising: by a media agent at a first computing device, populating acache storage area at the media agent with data blocks read during afile indexing operation of a backup copy, wherein the backup copy wasgenerated in a block-level backup operation of primary data, and whereinthe populating comprises: by the media agent, receiving an indicationthat the file indexing operation has been initiated by a secondcomputing device, receiving a first read request issued by the fileindexing operation for a first data block of the backup copy, (i) if themedia agent determines that the first data block is in the cache storagearea, retrieving the first data block from the cache storage area, and(ii) if the media agent determines that the first data block is not inthe cache storage area, retrieving the first data block from the backupcopy stored on backup media, adding the first data block to the cachestorage area, and updating a cache-index to indicate that the first datablock is in the cache storage area; wherein the first data block andother data blocks added to the cache storage area during the fileindexing operation are available to be read from the cache storage areaand not from the backup copy for subsequent live browse operations ofthe backup copy; and wherein the first computing device comprises one ormore hardware processors and wherein the second computing devicecomprises one or more hardware processors.
 2. The method of claim 1further comprising: by the media agent, receiving a second read requestfor the first data block of the backup copy issued by a subsequent livebrowse operation of the backup copy, and based on using the cache-indexto determine that the first data block is in the cache storage area,retrieving the first data block from the cache storage area and not fromthe backup copy.
 3. The method of claim 1 further comprising: by themedia agent during a subsequent incremental block-level backup operationof the primary data: identifying that a changed version of the firstdata block is being backed up to a second backup copy, based on usingthe cache-index, determining that the first data block is in the cachestorage area, adding the changed version of the first data block to thecache storage area, and updating the cache-index to indicate that thechanged version of the first data block is in the cache storage area;and wherein in a live browse operation of the second backup copy, thechanged version of the first data block is retrieved from the cachestorage area and not from the second backup copy.
 4. The method of claim3 further comprising during the subsequent incremental block-levelbackup operation that generates the second backup copy: in abackup-index that tracks where data blocks are stored on backup media,flagging the changed version of the first data block as a data blocksuitable for the cache storage area; and wherein flags in thebackup-index are used in a subsequent file indexing operation of a thirdbackup copy of the primary data to pre-fetch from the third backup copysecond data blocks corresponding to data blocks of the second backupcopy flagged as suitable for the cache storage area, including the firstdata block, and wherein the pre-fetch is performed in a sequential orderaccording to where the second data blocks are stored on the backupmedia.
 5. The method of claim 4, wherein the pre-fetch enables thesubsequent file indexing operation of the third backup copy to completesooner as compared to on demand serving read requests issued by thesubsequent file indexing operation.
 6. The method of claim 3 furthercomprising during the subsequent incremental block-level backupoperation that generates the second backup copy: in a backup-index thattracks where data blocks are stored on backup media, flagging thechanged version of the first data block as a data block suitable for thecache storage area; and wherein flags in the backup-index are usedinstead of the cache-index in a subsequent live browse operation of thesecond backup copy to determine whether to add a given data block of thesecond backup copy to the cache storage area for later retrievaltherefrom instead of from the backup media.
 7. The method of claim 1,wherein a virtual machine generates the primary data, which resides on avirtual disk.
 8. The method of claim 1, wherein a virtual machinegenerates the primary data, which resides in a cloud storageenvironment.
 9. The method of claim 1, wherein one or more applicationsthat execute on a third computing device, distinct from the firstcomputing device, generate the primary data.
 10. The method of claim 1,wherein the backup copy is stored at one or more of: a cloud storageenvironment and magnetic tape.
 11. A computer-implemented method forpopulating a cache storage area in a data storage management system, themethod comprising: by a media agent, populating a cache storage areawith data blocks read during a first live browse operation of a backupcopy, wherein the backup copy was generated in a block-level backupoperation of primary data, and wherein the populating comprises: by themedia agent, receiving a first read request issued by the first livebrowse operation for a first data block of the backup copy, and (i) ifthe media agent determines that the first data block is in the cachestorage area, retrieving the first data block from the cache storagearea, and (ii) if the media agent determines that the first data blockis not in the cache storage area, retrieving the first data block fromthe backup copy, adding the first data block to the cache storage area,and updating a cache-index to indicate that the first data block is inthe cache storage area; by the media agent during a subsequentincremental block-level backup operation of the primary data:identifying that a changed version of the first data block is beingbacked up to a second backup copy, determining that the first data blockis in the cache storage area, in a backup-index that tracks where datablocks are stored on backup media, flagging the changed version of thefirst data block as a data block suitable for the cache storage area,adding the changed version of the first data block to the cache storagearea, and updating the cache-index to indicate that the changed versionof the first data block is in the cache storage area; wherein in asubsequent file indexing operation of the second backup copy, thechanged version of the first data block is retrieved from the cachestorage area and not from the second backup copy on the backup media;and wherein the media agent executes on a first computing devicecomprising one or more hardware processors.
 12. The method of claim 11,wherein a data agent associated with the primary data indicates to themedia agent that the changed version of the first data block is beingbacked up to the second backup copy.
 13. The method of claim 11 furthercomprising: by the media agent, storing a third backup copy of theprimary data to backup media, wherein the third backup copy is generatedby a full block-level backup operation; and in a file indexing operationof the third backup copy: identifying one or more data blocks of thethird backup copy that are flagged in the backup-index as suitable forthe cache storage area, defining a sequential order for the one or moredata blocks of the third backup copy according to where they are storedon the backup media, sequentially retrieving the one or more data blocksfrom the backup media according to the sequential order, adding the oneor more data blocks to the cache storage area, updating the cache-indexto indicate that the one or more data blocks of the third backup copyare in the cache storage area, serving read requests issued by the fileindexing operation of the third backup copy for the one or more datablocks from the cache storage area, and retrieving on demand other datablocks needed for the file indexing operation of the third backup copyfrom the backup media to serve read requests issued by the file indexingoperation for the other data blocks; wherein the sequentiallyretrieving, adding, and serving of the one or more data blocks from thecache storage area is faster than on demand retrieving the one or moredata blocks from the third backup copy on the backup media to serve theread requests issued by the file indexing operation for the one or moredata blocks.
 14. The method of claim 11, wherein the backup media ispart of a cloud storage environment.
 15. The method of claim 11, whereinthe backup media comprises magnetic tape.
 16. The method of claim 11,wherein a virtual machine generates the primary data, which resides on avirtual disk.
 17. The method of claim 11, wherein a virtual machinegenerates the primary data, which resides in a cloud storageenvironment.
 18. The method of claim 11, wherein one or moreapplications that execute on a second computing device distinct from thefirst computing device generate the primary data.
 19. The method ofclaim 11, wherein a pseudo-disk driver is interposed between a secondcomputing device that initiates the first live browse operation and themedia agent, and wherein the first data block is transmitted by themedia agent to the pseudo-disk driver in response to an indication thatthe second computing device initiated the first live browse operation,and wherein the pseudo-disk driver responds to read requests of thefirst live browse operation issued by the second computing device; andwherein the pseudo-disk driver executes on one of: the first computingdevice that hosts the media agent, the second computing device thatinitiates the first live browse operation, and a third computing devicedistinct from the first and the second computing devices.
 20. The methodof claim 19, wherein the pseudo-disk driver serves read requests of thefirst live browse operation from a first storage area that comprisesdata blocks received from the media agent, including the first datablock, and wherein the pseudo-disk driver stores data blocks from writeoperations issued by the first live browse operation to a second storagearea whose contents are discarded after the second computing deviceterminates the first live browse operation.